Sipay Business Api
English
  • Turkish
  • English
  1. Transaction Data
Sipay Business Api
English
  • Turkish
  • English
  • Overview
    • Sipay Business API
    • Partner Wallet Flow Guide
  • Authentication
    • Get Access Token
      POST
  • Account
    • Get Business Account
      POST
    • Check Personal Wallet (AccountNumber)
      POST
    • Check Personal Wallet (PhoneNumber)
      POST
  • Wallet
    • Create Wallet For Business Account
      POST
    • Wallet Info
      POST
    • Wallet List By Filter
      POST
  • Transaction
    • Business To Personal Transfer
      POST
    • Business To Business Transfer
      POST
    • Send Money To Bank Account
      POST
    • Transfer To Virement
      POST
  • Transaction Data
    • Transaction Type Code List
    • How to payout status check?
    • Summary Record By Filter
      POST
    • Get Request Withdraw List By Filter
      POST
    • Get Request Withdraw By Ext Id
      POST
    • Transaction Receipt
      POST
  • Webhook
    • Bank Transfer Webhook
    • Top-up Webhook
    • Failed Top-Up Webhook
  1. Transaction Data

How to payout status check?

Summary#

After POST /v1/Transaction/SendMoneyToBankAccount (code 100), the full transaction record may appear with a delay. Seeing code 312 in SummaryRecordByFilter right after is expected.
Recommended flow to check the status after SendMoneyToBankAccount:
1
Start the payout
POST /v1/Transaction/SendMoneyToBankAccount — keep your ext_transaction_id.
(Required fields and test values are documented.)
2
Primary signal: Webhook
Wait for the payout webhook Bank Transfer Webhook
If you like, we can quickly configure the webhook on your side.
3
Secondary check (if no webhook / as a fallback)
Poll by ext_transaction_id using:
POST /v1/TransactionData/GetRequestWithdrawByExtId → check process_level_status
0 = Pending
1 = Completed (funds sent) → treat as pay-out success
2 = Rejected
3 = Failed
Docs: https://docs.businessapi.sipay.com.tr/en/get-request-withdraw-by-ext-id-17972402e0
4
Final check (reporting)
POST /v1/TransactionData/SummaryRecordByFilter with your ext_transaction_id (plus normal paging/sort).
Use transaction_status_id (20 = Completed) and rely on completed_date_utc as the completion time
How long can an operation remain with code 312 after code 100?
It depends on the bank and the current processing load. In most cases it's 2–3 seconds, but in peak times it can take up to ~20 minutes.
What does code 100 mean?
What does code 312 mean after 100?
When does SummaryRecord show the transaction?
Why do we see 503 with varying messages?
Previous
Transaction Type Code List
Next
Summary Record By Filter
Built with