Payouts to bank accounts in Singapore
Overview
Introduction
Payouts to bank accounts in Singapore is a payment method which allows you to process payments in Singapore dollars by using bank accounts in Singapore. This method supports payouts.
This article provides information about working with the Payouts to bank accounts in Singapore method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow.
General information
| Payment method type | bank payments | 
|---|---|
| Payment instruments | bank accounts | 
| Countries and regions | SG | 
| Payment currencies | SGD | 
| Currency conversion | – | 
| One-time purchases | – | 
| Credential-on-file purchases | – | 
| Full refunds | – | 
| Partial refunds | – | 
| Payouts | + | 
| Chargebacks | – | 
| Notes | payouts to bank accounts may be performed through banks directly or through other organisations that provide financial services in Singapore (details) | 
| Onboarding and access fee | refer to your ecommpay account manager | 
Interaction diagram
Payment processing by using the Payouts to bank accounts in Singapore method involves the merchant's web service, one of ecommpay interfaces, the ecommpay payment platform, and technical facilities of the provider service.
Operations support
Various platform interfaces can be used to process payments and perform operations using the Payouts to bank accounts in Singapore method. Payouts can be processed by using Gate and Dashboard. At the same time, regardless of the interfaces used, the following amount limits are applicable.
The following properties and limitations apply to the Payouts to bank accounts in Singapore method.
| Amounts, SGD ¹ | Times ² | |||
|---|---|---|---|---|
| minimum | maximum | base | threshold | |
| Payouts | 1.00 | 200,000.00 | within 1 minute | within 45 minutes | 
- Limits on payment amounts may be set by the banks and organisations that perform the payouts. Refer to your ecommpay account manager for information about the limits on the amounts within a certain project.
- The base and threshold times are defined as follows: - The base time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the web service. The base time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from the customer is required). Use the base time to estimate when to react to the absence of payment result callbacks or when to check payment status (details).
- The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the web service receives the callback with the payment result. A payment is automatically assigned the declinestatus if it wasn't processed within the threshold time. For individual customisation of the threshold time limit, contact ecommpay technical support.
 
Processing scenarios
To initiate a payout by using the Payouts to bank accounts in Singapore method, you need to notify the customer via the merchant's web service.
At the same time, one of the specifics of working with this method is that payouts to bank accounts may be performed through banks directly or through other organisations that provide financial services in Singapore. Thus, for each payout with this method, a certain bank or an organisation must be specified. When payments are initiated through Gate, the bank or organisation must be selected on the side of the web service and the identifier of this bank or organisation must be specified in the requests. Ways of using these identifiers are described in the next subsection, Supported banks and other organisations.
Supported banks and other organisations
The following table lists the names and identifiers of banks and other organisations supported by the Payouts to bank accounts in Singapore method. Keep in mind that this list is presented for informational purposes.
| Bank | ID | 
|---|---|
| Anext Bank | 88641 | 
| ANZ | 88651 | 
| Bank Of China | 88661 | 
| BEA Singapore | 88861 | 
| BNP Paribas | 88671 | 
| Citibank N.A. SG Branch | 88741 | 
| CIMB | 88681 | 
| Citibank Singapore Limited | 88151 | 
| DBS Bank | 57001 | 
| Deutsche Bank | 88701 | 
| Gpay Network Bank (S) | 88881 | 
| Green Link Digital Bank | 88711 | 
| GXS Bank | 88721 | 
| HL Bank | 88731 | 
| HSBC | 88691 | 
| ICBC | 88761 | 
| ICICI Bank | 88751 | 
| J.P.Morgan | 88771 | 
| Liquid Group | 88891 | 
| MariBank | 88781 | 
| MatchMove | 88901 | 
| Maybank | 88791 | 
| Mizuho Bank Limited Singapore Branch | 88141 | 
| MUFG | 88801 | 
| NIUM | 88911 | 
| OCBC | 57011 | 
| RHB Bank | 88811 | 
| SIB Singapore | 88831 | 
| Sing Investments & Finance Ltd | 88841 | 
| Singtel Dash (Singcash Ltd) | 88921 | 
| SMBC | 88851 | 
| Standard Chartered Bank | 88821 | 
| Trust Bank | 88871 | 
| UOB | 57021 | 
| Wise | 88931 | 
| Xfers | 88941 | 
Since the list of available banks and organisations may change over time, it is recommended to send a POST request to the /v2/info/banks/singapore/payout/list endpoint to obtain up-to-date information. This endpoint belongs to the /v2/info/banks/{payment_method}/{operationType}/list group of the Gate API. The request must contain the project and payment identifiers, signature, currency code, and payment amount, as shown in the example. Specify real payment data if possible. However, random values are also allowed.
{
    "general": {
        "project_id": 200,
        "payment_id": "ORDER_155860015",
        "signature": "K6jllym+PtObocZtr345st...=="
    },
    "payment": {
        "amount": 10000,
        "currency": "SGD"
    }
}
      If you have any questions about working with banks and other organisations supported by the Payouts to bank accounts in Singapore method, refer to your ecommpay account manager.
Payouts by using Gate
General information
To process a payout through Gate by using the Payouts to bank accounts in Singapore method, send a request with all required parameters and signature to the ecommpay URL and receive a callback with the result. The full sequence and special aspects of payout processing are provided below.
- A customer initiates a payout by using the Payouts to bank accounts in Singapore method in the web service.
- The web service sends the request for processing the payout by using Gate to the specified ecommpay URL.
- The payment platform receives the request.
- The payment platform validates the required parameters and signature in the request.
- The payment platform sends the response to the web service with information about the receipt of the request and its validity (details).
- The payment platform performs further processing of the request (with parameter consistency check) and sends it to the provider service.
- The payout is processed on the side of the provider service.
- The provider service sends the result notification to the payment platform.
- The payment platform sends the result callback to the web service.
- The customer receives the payout result information from the web service.
Information about the formats of requests and callbacks used for processing payouts by using the Payouts to bank accounts in Singapore method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.
Request format
There are several things you need to consider when sending payout requests by using the Payouts to bank accounts in Singapore method:
- To initiate each payout send a separate POST request to the /v2/payment/banks/singapore/payoutendpoint. This endpoint belongs to the group /v2/payment/banks/{payment_method}/payout.
- Each request must include the following objects and parameters: - Object general—general payout information:- project_id—project identifier obtained from ecommpay during integration
- payment_id—payment identifier unique within the project
- signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification) details
 
- Object payment—payment information:- amount—payout amount in the smallest currency unit
- currency—payout currency code in the ISO-4217 alpha-3 format
 
- Object customer—customer information:- id—customer identifier unique within the project
- ip_address—customer IP address relevant for the initiated payout
 
- Object account—account information:- number—bank account number of the customer (without hyphens and other separators).
 
 
- Object 
- The request must include the full name of the bank account holder in one of the two following objects (at the merchant's discretion) with all parameters specified for this object:- Object customer—customer information:- first_name—customer first name
- last_name—customer last name
 
- Object account—account information:- customer_name—account holder full name
 
 
- Object 
- The request must include information about the bank (or other organisation through which the payout is made) in one of the two parameters (at the merchant's discretion) of the accountobject:- bank_id—identifier of the bank (or other organisation through which the payout is made) used in the ecommpay payment platform
- bank_code—international identifier (BIC or SWIFT) of the bank or other organisation through which the payout is made
 
- The currency of the payment can only be SGD.
- Additionally, any other parameters included in the specification can be used.
Thus, a correct payout request by using the Payouts to bank accounts in Singapore method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and IP address, information about the bank or other organisation through which the payout is made, information about the customer account, including the full name of the account holder, signature, and may include any other additional parameters.
The following is the example of the request for a payout in case when the recipient's bank is specified by using its identifier used in the ecommpay payment platform and the account object includes the full name of the account holder.
{
  "general": {
    "project_id": 567890,
    "payment_id": "test1234567890",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 12300,
    "currency": "SGD"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "bank_id": "57001",
    "customer_name": "John Doe",
    "number": "0788883332"
  }
}
            The following is the example of the data in the customer and account objects in the request for a payout in case when the customer object includes the full name of the account holder.
}, "customer": { "id": "customer123", "ip_address": "192.0.2.0", "first_name": "John", "last_name": "Doe" }, "account": { "bank_id": "57001", "number": "0788883332" } }
The following is the example of the data in the account object in the request for a payout in case when the recipient's bank is specified by using the international identifier (BIC or SWIFT).
}, "account": { "bank_code": "DBSSSGSGXXX", "customer_name": "John Doe", "number": "0788883332" } }
Callback format
The Payouts to bank accounts in Singapore method uses the standard format for callbacks to deliver payout results. For more information, see Handling callbacks.
The following is the example of a callback with information about a 123.00 SGD payout made for the customer123 customer in the 12345 project.
 {
        "project_id": 12345,
        "payment": {
            "id": "payment4444",
            "type": "payout",
            "status": "success",
            "date": "2025-09-12T13:28:58+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 12300,
                "currency": "SGD"
            },
            "description": "payout"
        },
        "account": {
            "number": "12-34-******5-67"
        },
        "customer": {
            "id": "customer123"
        },
        "provider_extra_fields": {
            "bank_trx_id": "IGef88425f-1234"
        },
        "operation": {
            "id": 9912000002236,
            "type": "payout",
            "status": "success",
            "created_date": "2025-09-12T13:22:15+0000",
            "date": "2025-09-12T13:28:58+0000",
            "request_id": "b54610e94a76",
            "sum_initial": {
                "amount": 12300,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 12300,
                "currency": "SGD"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 21635,
                "payment_id": "IGef88425f-1234",
                "date": "2025-09-12T13:28:34+0000",
                "auth_code": ""
            },
        },
        "signature": "10zy9TNiJLT0P/+EOrpMkoW80mynkaQfSAUJpfQ=="
    }                 
}
            The following is the example of a callback with information about a declined payout.
{
        "project_id": 433772,
        "payment": {
            "id": "PAYOUT78966",
            "type": "payout",
            "status": "decline",
            "date": "2025-09-07T09:44:43+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 12300,
                "currency": "SGD"
            },
            "description": ""
        },
        "account": {
            "number": "***6789"
        },
        "customer": {
            "id": "customer123"
        },
        "operation": {
            "id": 533000002202,
            "type": "payout",
            "status": "decline",
            "date": "2025-09-07T09:44:43+0000",
            "created_date": "2022-09-07T09:44:43+0000",
            "request_id": "205d3536a91f4737d679ae44f5c707e248258224fe3f6",
            "sum_initial": {
                "amount": 12300,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 12300,
                "currency": "SGD"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 21635,
                "payment_id": "",
                "auth_code": ""
            },
        },
        "signature": "j4cxKDvx0EtSJw0bHot6v83rzDMlinxE915lAWGHKVjurpQ=="
    }
}
            Useful links
The following articles can be useful when implementing payouts via Gate:
- Interaction concepts—about the interaction with the payment platform by using Gate.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment processing—about the types, processing models, and possible statuses of supported payments and operations.
- Payouts—about processing of payouts by using Gate.
- Handling operation processing information—about error and response codes that are used in the payment platform to record information about performing of operations.
Payouts by using Dashboard
When working with Dashboard, you can process single and mass payouts by using the Payouts to bank accounts in Singapore method.
- To process a single payout, open the payout form, specify all required parameters (including the payment method), send a request and verify that the payout has been processed.
- 
                To process a mass payout, prepare and upload a file with information about all target payouts, send a batch request, and verify that the payouts have been processed. Use a CSV file structured according to the requirements presented in the Mass payments data section. The payout parameters must comply with the requirements (you do not have to generate a signature because it is specified by Dashboard). 
More information about processing payouts by using Dashboard is presented in a separate section.
Analysis of payments results
To analyse information about payments made with the Payouts to bank accounts in Singapore method and methods, you can use:
- Dashboard interface toolkit with various lists and analytic panels.
- Reports in CSV file format, available via the Reports section (one-time and periodically).
- Data in JSON format, sent by program requests to a specified URL available by using the Data API interface.
If you have any questions, refer to the documentation (Dashboard and Using Data API) and ecommpay technical support.