Singapore Online Banking
Overview
Introduction
Singapore Online Banking is a payment method that uses the online banking mechanism for payments in Singapore dollars through banks of Singapore. This method supports purchases and payouts.
This article provides information about working with the Singapore Online Banking 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 | on the ecommpay side |
One-time purchases | + |
Credential-on-file purchases | – |
Full refunds | – |
Partial refunds | – |
Payouts | + |
Chargebacks | – |
Notes | Payment Page supports different bank selection options. |
Onboarding and access fee | refer to your ecommpay account manager |
Interaction diagram
Payment processing by using the Singapore Online Banking method involves the merchant's web service, one of ecommpay interfaces, the ecommpay payment platform, and technical facilities of the supported banks.
Operations support
Various platform interfaces can be used to process payments and perform operations using the Singapore Online Banking method. Purchases can be processed by using Payment Page and Gate, payouts—by using Gate and Dashboard. At the same time, regardless of the interfaces used, the following amount limits are applicable.
When working with the Singapore Online Banking the following amount limits are applicable.
Amounts, SGD | ||
---|---|---|
minimum | maximum | |
Purchases | 10.00 | 30,000.00 |
Payouts | 10.00 | 10,000.00 |
Keep in mind that payment processing times depend on banks, that support purchases by using this payment method.
Processing scenarios
To perform a purchase by using the Singapore Online Banking method, you need to redirect customer to the banks that support the work with this method. To initiate a payout, you need to notify the customer via the web service.
The customer payment scenario via Payment Page (in the basic case where the customer chooses the method and bank and is redirected from the final page of the payment form to the web service) looks like this.
General scenarios of processing purchases and payouts can be presented as follows.
At the same time, the specifics of working with the method include the necessity of selecting a bank for each payment. When Payment Page is used for payment processing, the customer usually selects a bank while already in the payment form. When Payment Page is opened with the method and bank preselected as well as when payments are initiated through Gate, the bank must be selected on the side of the web service and the identifier of this bank must be specified in requests. Possible options for bank selection when working with Payment Page are described in Purchases by using Payment Page, ways of using bank identifiers—in the next subsection, Supported banks.
At the same time, different options for selecting a bank are supported for payments by using this method; they are described in the Purchases by using Payment Page section of this article.
Supported banks
The following table lists the names and identifiers of banks supported by the Singapore Online Banking method. Keep in mind that this list is presented for informational purposes.
Bank | ID | Purchase | Payout |
---|---|---|---|
DBS Bank Singapore | 57001 | + | + |
OCBC Bank Singapore | 57011 | + | + |
UOB Singapore | 57021 | + | + |
Since the list of available banks may change over time, it is recommended to send a POST request to the /v2/info/banks/singapore/sale/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.
If you have any questions about working with banks supported by the Singapore Online Banking method, refer to your ecommpay account manager.
Purchases by using Payment Page
General information
To process a purchase through Payment Page by using the Singapore Online Banking method, the merchant's web service is required to send a request with all required parameters and signature to the ecommpay URL and receive a callback with the result. At the same time, various options are available for choosing a method and a bank by specifying the appropriate parameters in queries. The full sequence and special aspects of purchase processing are provided below.
Generally, when a customer confirms their intention to pay on the side of the web service, they are redirected to Payment Page where they select the payment method and, in the case of working with the Singapore Online Banking method, additionally select one of the available banks. However, in some situations, other options for choosing a payment method and bank may be relevant. For example, upon opening Payment Page, you can immediately redirect the customer to the bank selection page or limit the list of supported banks for a particular payment and display only target bank selection buttons to the customer. The specific option of selecting the payment method and bank is determined depending on the parameters specified in the request for opening Payment Page (detailes). The following options are available:
- 1—when the payment form is opened, it sequentially displays separate pages for selecting a method and a bank. Then the customer selects the method and the bank (this option is used by default).
- 2—when the payment form is opened, the buttons for selecting other methods and banks supported by this method are displayed on one page. Then the customer selects one of these banks.
- 3—when the payment form is opened, it displays a page with buttons for selecting all available banks for this method. Then the customer selects one of these banks.
- 4—when the payment form is opened, it displays a page with buttons for selecting only specific banks supported by this method. Then the customer selects one of these banks.
- 5—when the payment form is opened, it displays a page requesting confirmation of redirection to the service of the specific bank. Then the customer confirms the redirection.
Information about the formats of requests and callbacks used for processing payments by using the Singapore Online Banking method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.
Request format
There are several things you need to consider when sending purchase requests by using the Singapore Online Banking method:
- The following parameters required for any payment must be specified:
project_id
—project identifier obtained from ecommpay during integrationpayment_id
—payment identifier unique within the projectpayment_currency
—payment currency code in the ISO-4217 alpha-3 formatpayment_amount
—payment amount in the smallest currency unitcustomer_id
—customer identifier unique within the project
- The following parameters required for any payment must be specified:
project_id
,payment_id
,payment_currency
,payment_amount
,customer_id
. -
The following are the bank selection options:
- Selecting the method and the bank on Payment Page (1)—the default option, applied if the
force_payment_method
parameter and thepayment_methods_options
object are not used. - Selecting a bank among other methods on Payment Page (2)—for this option in the
payment_methods_options
object specify theonline_singapore_banks
object containing thesplit_banks
parameter with the valuetrue
:"payment_methods_options": "{\"online_singapore_banks\": {\"split_banks\": true}}"
- Selecting a bank among all available ones on Payment Page (3)—for this option specify the method code
online-singapore-banks
in theforce_payment_method
parameter. - Selecting a bank among specific ones on Payment Page(4)—for this option specify the following:
- the
online_singapore_banks
code in theforce_payment_method
parameter - the
payment_methods_options
object with theonline_singapore_banks
object that contains thesplit_banks
parameter with the valuetrue
and abanks_id
object with an array containing the target bank identifiers:"payment_methods_options": "{\"online_singapore_banks\": {"\split_banks\": true, "banks_id": [57001, 57011]}}"
- the
- Confirming redirection to the service of the specific bank on Payment Page (5)—for this option specify the following:
- the
online_singapore_banks
code in theforce_payment_method
parameter - the
payment_methods_options
object with theonline_singapore_banks
object that contains thesplit_banks
parameter with the valuetrue
and abanks_id
object with an array containing the target bank identifier:"payment_methods_options": "{\"online_singapore_banks\": {"\split_banks\": true, "banks_id": [57001]}}"
- the
- Selecting the method and the bank on Payment Page (1)—the default option, applied if the
- Additionally, any other parameters available for working with Payment Page can be used (details).
- After all target parameters are specified, generate a signature (details).
Thus, a correct request for opening the payment form using the Singapore Online Banking method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier, and signature.
At the same time, in case of selecting a bank among specific banks (4), the request for opening Payment Page may contain additional data.
Callback format
The Singapore Online Banking method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.
The following is the example of a callback with information about a 340.00 SGD
purchase made by the customer55
customer in the 55120
project.
The following is the example of a callback with information about a declined purchase.
Useful links
The following articles can be useful when implementing purchases via Payment Page:
- Interaction concepts—about the interaction with the payment platform by using Payment Page.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Purchases by using Gate
General information
To process a purchase through Gate by using the Singapore Online Banking method, the merchant's web service is required to do the following:
- Send a request with all the required parameters and signature to the ecommpay URL.
- Receive an intermediate callback from the payment platform and redirect the customer to the service of the bank, which supports payment processing by using the Singapore Online Banking method.
- Receive the final callback from the payment platform.
The full sequence and special aspects of purchase processing are provided below.
Information about the formats of requests and callbacks used for processing payments by using the Singapore Online Banking 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 purchase requests by using the Singapore Online Banking method:
- To initiate each purchase, send a separate POST request to the
/v2/payment/banks/singapore/sale
endpoint. This is an online banking request group: /v2/payment/banks/{payment_method}/sale. - Each request must include the following objects and parameters:
- Object
general
—general purchase information:project_id
—project identifier obtained from ecommpay during integrationpayment_id
—payment identifier unique within the projectsignature
—request signature generated after all required parameters are specified (details—in the Signature generation and verification) (details)
- Object
payment
—payment information:amount
—payment amount in the smallest currency unitcurrency
—payment currency code in the ISO-4217 alpha-3 format
- Object
customer
—customer information:id
—customer identifier unique within the projectip_address
—customer IP address relevant for the initiated payment
account
—object with customer account information:bank_id
— bank ID.
- Object
- Additionally, any other parameters included in the specification can be used.
Thus, a correct purchase request by using the Singapore Online Banking method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and IP address, bank ID, as well as signature.
Formats of intermediate callbacks for customer redirection
Each payment made with the Singapore Online Banking method requires redirection of customers from the merchant's web service to the Singapore Online Banking service. To redirect a customer it is necessary to receive an intermediate callback from the payment platform and use the information included in the redirect_data
object. The format of such callbacks is standard (details), and the following objects and parameters are included in the redirect_data
object:
body
—object with data to be sent in the request bodymethod
—parameter specifying the HTTP method for sending the request (GET
orPOST
)url
—parameter containing a link for redirection
Final callback format
The Singapore Online Banking method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.
The following is the example of a callback with information about a 340.00 SGD
purchase made by the customer55
customer in the 55120
project.
The following is the example of a callback with information about a declined purchase.
Useful links
The following articles can be useful when implementing purchases 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 models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Payouts by using Gate
General information
To process a payout through Gate by using the Singapore Online Banking 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.
Information about the formats of requests and callbacks used for processing payouts by using the Singapore Online Banking 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 Singapore Online Banking method:
- To initiate each payout send a separate POST request to the
/v2/payment/banks/singapore/payout
endpoint. This is an online banking request 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 integrationpayment_id
—payment identifier unique within the projectsignature
—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 unitcurrency
—payout currency code in the ISO-4217 alpha-3 format
- Object
customer
—customer information:id
—customer identifier unique within the projectip_address
—customer IP address relevant for the initiated payout
- Object
account
—account information:number
—account numbercustomer_name
—name of bank account holderbank_id
—bank ID
- Object
- Additionally, any other parameters included in the specification can be used.
Thus, a correct payout request by using the Singapore Online Banking method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and IP address, name of bank account holder and bank ID and signature.
Callback format
The Singapore Online Banking method uses the standard format for callbacks to deliver payout results. For more information, see Callbacks.
The following is the example of a callback with information about a 560.00 SGD
payout made for the customer123
customer in the 55120
project.
The following is the example of a callback with information about a declined payout as a invalid bank ID was sent in the request.
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 models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- Payouts—about processing of payouts by using Gate.
- Information of operations performing—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 Singapore Online Banking 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 Singapore Online Banking 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.