Singapore Online Banking

Overview

Introduction

Singapore Online Banking is a payment method that uses the online banking mechanism for payments through banks of Singapore. This method supports purchases by using Payment Page and Gate, payouts by using Gate and Dashboard.

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
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 some the 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 Singapore Online Banking service.



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 properties and limitations are applicable to all operationsapplicable.

  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 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 Purchase by using Payment Page.

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.

Table 1. List of banks
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.

Figure: Example of data in the request for receiving the list of banks

{
    "general": {
        "project_id": 200,
        "payment_id": "ORDER_155860015",
        "signature": "K6jllym+PtObocZtr345st...=="
    },
    "payment": {
        "amount": 16000,
        "currency": "SGD"
    }
}

Figure: Example of data in the response containing the information about banks

[
  {
    "id": 57001, // Bank ID
    "abbr": "DBSSGD", // Bank abbreviation (for internal use)
    "name": "DBS Bank Singapore", // International bank name
    "nativeName": "DBS Bank Singapore", // Local bank name
    "currencies": [ // Array with information about the currencies supported by the bank
      {
        "id": 1087, // Currency ID in the payment platform
        "alpha_3_4217": "SGD", // ISO-4217 alphabetic currency code
        "number_3_4217": "702", // ISO-4217 numeric currency code
        "exponent": 2 // The number of decimal units of the currency
      }
    ]
  },
]

If you have any questions about working with banks supported by the Singapore Online Banking method, refer to your ecommpay account manager.

Purchase by using Payment Page

General information

To process a purchase through Payment Page by using the Singapore Online Banking method, the merchant 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. The Singapore Online Banking method can also be set as preselected payment method when Payment Page opens (details). The full sequence and special aspects of purchase processing are provided below.



Figure: Purchase processing by using Payment Page: step-by-step description

  1. A customer initiates a purchase in the web service.
  2. The web service sends the request for opening Payment Page to the specified ecommpay URL.
  3. The request for opening Payment Page is sent to the payment platform.
  4. The payment platform receives the request and validates the required parameters and signature.
  5. Payment Page is generated based on the project settings and parameters specified in the request.
  6. Payment Page is displayed to the customer.
  7. The customer selects the Singapore Online Banking method and one of the supported banks.
  8. The request for processing the payment is received by the payment platform.
  9. The payment platform processes the request and sends it to the bank service.
  10. The request is processed on the side of the bank service.
  11. The data for redirecting the customer to the bank website is sent from the bank service to the payment platform.
  12. The data for redirecting the customer is sent from the payment platform to Payment Page.
  13. The customer is redirected to the bank website.
  14. The customer completes all required payment steps.
  15. The purchase is processed on the side of the bank service.
  16. The result information is displayed to the customer in the bank website.
  17. The customer is redirected to Payment Page.
  18. The bank service sends a notification about the result to the payment platform.
  19. The payment platform sends the payment result callback to the web service.
  20. The payment platform sends the result information to Payment Page.
  21. The result information is displayed to the customer on Payment Page.

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 (more details below). The following options are available: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 (more details below). 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:

  1. The following parameters required for any payment must be specified:
    • project_id—project identifier obtained from ecommpay during integration
    • payment_id—payment identifier unique within the project
    • payment_currency—payment currency code in the ISO-4217 alpha-3 format
    • payment_amount—payment amount in the smallest currency unit
    • customer_id—customer identifier unique within the project
  2. The following parameters required for any payment must be specified: project_id, payment_id, payment_currency, payment_amount, customer_id.
  3. The following are the bank selection options:

    1. Selecting the method and the bank on Payment Page (1)—the default option, applied if the force_payment_method parameter and the payment_methods_options object are not used.
    2. Selecting a bank among other methods on Payment Page (2)—for this option in the payment_methods_options object specify the online_singapore_banks object containing the split_banks parameter with the value true:
      "payment_methods_options": {"online_singapore_banks": {"split_banks": true}}
    3. Selecting a bank among all available ones on Payment Page (3)—for this option specify the method code online-singapore-banks in the force_payment_method parameter.
    4. Selecting a bank among specific ones on Payment Page(4)—for this option specify the following:
      • the online_singapore_banks code in the force_payment_method parameter
      • the payment_methods_options object with the online_singapore_banks object that contains the split_banks parameter with the value true and a banks_id object with an array containing the target bank identifiers:
        "payment_methods_options": {"online_singapore_banks": {"split_banks": true, "banks_id": [57001, 57011]}}
    5. 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 the force_payment_method parameter
      • the payment_methods_options object with the online_singapore_banks object that contains the split_banks parameter with the value true and a banks_id object with an array containing the target bank identifier:
        "payment_methods_options": {"online_singapore_banks": {"split_banks": true, "banks_id": [57001]}}
  4. Additionally, any other parameters available for working with Payment Page can be used. See Parameters for opening payment form for information on all available parameters.Additionally, any other parameters available for working with Payment Page can be used (details).
  5. After all target parameters are specified, create 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.

{
   "project_id": 55120,
   "payment_id": "58550",
   "payment_amount": 34000,
   "payment_currency": "SGD",
   "customer_id": "customer55",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

At the same time, in case of selecting a bank among specific banks (4), the request for opening Payment Page may contain additional data.

{
   "project_id": 55120,
   "payment_id": "58550",
   "payment_amount": 34000,
   "payment_currency": "SGD",
   "customer_id": "customer55",
   "force_payment_method": "online-singapore-banks",
   "payment_methods_options": {"online_singapore_banks": {"split_banks": true, "banks_id": [57001, 57011, 57021]}}
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

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.

Figure: Example of data in a purchase callback

{
        "project_id": 55120,
        "payment": {
            "id": "58550",
            "type": "purchase",
            "status": "success",
            "date": "2022-08-26T11:06:48+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 34000,
                "currency": "SGD"
            },
            "description": "PAYMENT_58550"
        },
        "customer": {
            "id": "customer55"
        },
        "operation": {
            "sum_initial": {
                "amount": 34000,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 34000,
                "currency": "SGD"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 1111,
                "payment_id": "76666444",
                "auth_code": ""
            },
            "id": 544440057601,
            "type": "sale",
            "status": "success",
            "date": "2022-08-26T11:06:48+0000",
            "created_date": "2022-08-26T10:57:40+0000",
            "request_id": "bd8da81f8b73a960160b0ec44b8e9dfc2-00016185..."
        },
        "signature": "ly/4qzq1eDzKI9nwJe7N8aA9JcAjXoDjreWr9876FKm3eO+gaMA=="
    }

The following is the example of a callback with information about a declined purchase.

Figure: Example of data in a declined purchase callback

{
        "project_id": 55541,
        "payment": {
            "id": "PAYMENT_2745550925",
            "type": "purchase",
            "status": "decline",
            "date": "2022-08-26T11:06:48+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 1000,
                "currency": "SGD"
            },
            "description": "PAYMENT_270925"
        },
        "customer": {
            "id": "424222"
        },
        "operation": {
            "sum_initial": {
                "amount": 1000,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "SGD"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 61112,
                "payment_id": "64534535318185",
                "auth_code": ""
            },
            "id": 16464535601,
            "type": "sale",
            "status": "decline",
            "date": "2022-08-26T11:06:48+0000",
            "created_date": "2022-08-26T10:57:40+0000",
            "request_id": "bd8daae913d8a81f8b73a960160b0ec44b8e9dfc2-00016185..."
        },
        "signature": "ly/4qzq1eDzKI9nwJe7N8aA9JcAjXoDjreWru++Oc+inFKm3eO+gaMA=="
    }

Useful links

The following articles can be useful when implementing purchases via Payment Page:

Purchase 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:

  1. Send a request with all the required parameters and signature to the ecommpay URL.
  2. Receive an intermediate callback from the payment platform and redirect the customer to the website of the bank, which supports payment processing by using the Singapore Online Banking method.
  3. Receive the final callback from the payment platform.

The full sequence and special aspects of purchase processing are provided below.



Figure: Purchase processing by using Gate: step-by-step description

  1. A customer initiates a purchase by using the Singapore Online Banking method in the web service.
  2. The web service sends the request for processing the purchase by using Gate to the specified ecommpay URL.
  3. The payment platform receives the request.
  4. The payment platform validates the required parameters and signature in the request.
  5. The payment platform sends the response to the web service with information about the receipt of the request and its validity (details).
  6. The payment platform performs further processing of the request (with parameter consistency check) and sends it to the Singapore Online Banking service.
  7. The request is processed on the bank service side.
  8. The bank service sends the redirection data to the selected bank website to the payment platform..
  9. The payment platform sends the callback with the redirection data to the selected bank website.
  10. The customer is redirected to the bank website.
  11. The customer completes all required payment steps.
  12. The purchase is processed on the side of the bank service.
  13. The result is displayed to the customer.
  14. The customer is redirected to the web service.
  15. The bank service sends the payment result notification to the payment platform.
  16. The payment platform sends the payment result callback to the web service.
  17. The customer receives the payment result information from the web service.

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:

  1. To initiate each purchase, send a POST request to the /v2/payment/banks/singapore/sale endpoint. This is an online banking request group: /v2/payment/banks/{payment_method}/sale.
  2. Each request must include the following objects and parameters:
    • Object general—general purchase information:
      • project_id—project identifier obtained from ecommpay during integration
      • payment_id—payment identifier unique within the project
      • signature—request signature created after all required parameters are specified (details—in the Signature generation and verification)
    • Object payment—payment information:
      • amount—payment amount in the smallest currency unit
      • currency—payment currency code in the ISO-4217 alpha-3 format
    • Object customer—customer information:
      • id—customer identifier unique within the project
      • ip_address—IP address relevant for the initiated payment
    • account—object with customer account information:
      • bank_id — bank ID.
  3. 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.

{
  "general": {
    "project_id": 55120,
    "payment_id": "5855055",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 34000,
    "currency": "SGD"
  },
  "account":{
    "bank_id": 140
   },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
}

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 body
  • method—parameter specifying the HTTP method for sending the request (GET or POST)
  • url—parameter containing a link for redirection

Figure: redirect_data example

"redirect_data": {
            "body": {},
            "method": "POST",
            "url": "https://www.example.com/payment.php"
        },

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.

Figure: Example of data in a purchase callback

{
        "project_id": 55120,
        "payment": {
            "id": "58550",
            "type": "purchase",
            "status": "success",
            "date": "2022-08-26T11:06:48+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 34000,
                "currency": "SGD"
            },
            "description": "PAYMENT_58550"
        },
        "customer": {
            "id": "customer55"
        },
        "operation": {
            "sum_initial": {
                "amount": 34000,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 34000,
                "currency": "SGD"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 1111,
                "payment_id": "76666444",
                "auth_code": ""
            },
            "id": 544440057601,
            "type": "sale",
            "status": "success",
            "date": "2022-08-26T11:06:48+0000",
            "created_date": "2022-08-26T10:57:40+0000",
            "request_id": "bd8da81f8b73a960160b0ec44b8e9dfc2-00016185..."
        },
        "signature": "ly/4qzq1eDzKI9nwJe7N8aA9JcAjXoDjreWr9876FKm3eO+gaMA=="
    }

The following is the example of a callback with information about a declined purchase.

Figure: Example of data in a declined purchase callback

{
        "project_id": 55541,
        "payment": {
            "id": "PAYMENT_2745550925",
            "type": "purchase",
            "status": "decline",
            "date": "2022-08-26T11:06:48+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 1000,
                "currency": "SGD"
            },
            "description": "PAYMENT_270925"
        },
        "customer": {
            "id": "424222"
        },
        "operation": {
            "sum_initial": {
                "amount": 1000,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "SGD"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 61112,
                "payment_id": "64534535318185",
                "auth_code": ""
            },
            "id": 16464535601,
            "type": "sale",
            "status": "decline",
            "date": "2022-08-26T11:06:48+0000",
            "created_date": "2022-08-26T10:57:40+0000",
            "request_id": "bd8daae913d8a81f8b73a960160b0ec44b8e9dfc2-00016185..."
        },
        "signature": "ly/4qzq1eDzKI9nwJe7N8aA9JcAjXoDjreWru++Oc+inFKm3eO+gaMA=="
    }

Useful links

The following articles can be useful when implementing purchases via Gate:

Payout 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.



Figure: Payout processing by using Gate: step-by-step description

  1. A customer initiates a payout by using the Singapore Online Banking method in the web service.
  2. The web service sends the request for processing the payout by using Gate to the specified ecommpay URL.
  3. The payment platform receives the request.
  4. The payment platform validates the required parameters and signature in the request.
  5. The payment platform sends the response to the web service with information about the receipt of the request and its validity (details).
  6. The payment platform performs further processing of the request (with parameter consistency check) and sends it to the bank service.
  7. The payout is processed on the side of the bank service.
  8. The bank service sends the result notification to the payment platform.
  9. The payment platform sends the result callback to the web service.
  10. 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 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:

  1. To initiate each payout send a POST request to the /v2/payment/banks/singapore/payout endpoint. This is an online banking request group: /v2/payment/banks/{payment_method}/payout
  2. 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 created after all required parameters are specified (details—in the Signature generation and verification)
    • 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—IP address relevant for the initiated payout
    • Object account—account information:
      • number—account number
      • customer_name—name of bank account holder
      • bank_id—bank ID
  3. 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.

{
  "general": {
    "project_id": 55120,
    "payment_id": "payment4444",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 56000,
    "currency": "SGD"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0",
  },
  "account": {
    "number": "55554598",
    "bank_id": 57001,
    "customer_name": "Putra account"
  }
}

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.

Figure: Example of data in a payout callback

 {
        "project_id": 55120,
        "payment": {
            "id": "payment4444",
            "type": "payout",
            "status": "success",
            "date": "2022-09-12T13:28:58+0000",
            "method": "Singapore Banks",
            "sum": {
                "amount": 56000,
                "currency": "SGD"
            },
            "description": "payout"
        },
        "account": {
            "number": "55554598",
            "bank_id": 57001
        },
        "customer": {
            "id": "customer123"
        },
        "operation": {
            "id": 9912000002236,
            "type": "payout",
            "status": "success",
            "date": "2022-09-12T13:28:58+0000",
            "created_date": "2022-09-12T13:22:15+0000",
            "request_id": "b54610e94a76",
            "sum_initial": {
                "amount": 56000,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 56000,
                "currency": "SGD"
            },
            "provider": {
                "id": 15599,
                "payment_id": "88PZTPH0NBON42",
                "date": "2022-09-12T13:28:34+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "qV2FRs/wxoOaywQS0GYQDi+6spZFbiRXxt8zG
                            10zy9TNiJLT0P/+EOrpMkoW80mynkaQfSAUJpfQ=="
    }

The following is the example of a callback with information about a declined payout as a invalid bank ID was sent in the request.

Figure: Example of data in a declined payout callback

{
        "project_id": 55120,
        "payment": {
            "id": "PAYOUT78966",
            "type": "payout",
            "status": "decline",
            "date": "2022-09-07T09:44:43+0000",
            "method": "Singapore banks",
            "sum": {
                "amount": 50000,
                "currency": "SGD"
            },
            "description": ""
        },
        "account": {
            "number": "666622",
            "bank_id": 67091
        },
        "customer": {
            "id": "68686"
        },
        "errors": [
            {
                "code": "57010",
                "message": "Bank ID not found",
                "description": "Gate. Bank ID was not found in request"
            }
        ],
        "operation": {
            "id": 533000002202,
            "type": "payout",
            "status": "decline",
            "date": "2022-09-07T09:44:43+0000",
            "created_date": "2022-09-07T09:44:43+0000",
            "request_id": "205d3536a91f4737d679ae44f5c707e248258224fe3f6",
            "sum_initial": {
                "amount": 50000,
                "currency": "SGD"
            },
            "sum_converted": {
                "amount": 50000,
                "currency": "SGD"
            },
            "provider": {
                "id": 1003,
                "payment_id": ""
            },
            "code": "2801",
            "message": "Bank ID not found"
        },
        "signature": "j4cxKDvx0EtSJw0bHot6v83rzDMlinxE915lAWGHKVjurpQ=="
    }

Useful links

The following articles can be useful when implementing payouts via Gate:

Payout 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 create a signature because it is specified by Dashboard).

More information 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 as well as other 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 by using the Data API interface (details).

If you have any questions, refer to the documentation (Dashboard and Using Data API) and ecommpay technical support.