Bank transfers in Thailand
Overview
Bank transfers in Thailand is a payment method that allows customers to perform payments by using local bank transfers via banking applications, online banking and payment terminals. You can perform purchases through this method by using Payment Page and Gate. Download the logo in vector format here. |
Payment method type | Bank transfers |
---|---|
Countries and regions | Thailand |
Payment currencies | THB |
Currency conversion | On the Monetix side |
Purchases | |
Payouts | |
COF payments | |
Full refunds | |
Partial refunds | |
Chargebacks | |
Special considerations |
|
Onboarding and access fee | *Refer to your Monetix key account manager |
Interaction diagram
Payment processing by using the Bank transfers in Thailand payment method requires merchant's web service, one of Monetix interfaces (Payment Page or Gate), and the Monetix payment platform, as well technical facilities of the provider.
Operations support
Interfaces | Amounts, THB | Times | |||||
---|---|---|---|---|---|---|---|
Payment Page | Gate | Dashboard | minimum | maximum | basic | threshold | |
Purchases | 100.00 | 500,000.00 | 1 minute | 30 minutes |
You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section and click the Payment methods tab.
Processing scenarios
In the Bank transfers in Thailand method, to perform a purchase operation, you need to redirect customer to the provider service.
Restrictions
The number of purchases using the Bank transfers in Thailand method for the same user (with the same customer_id
) for specific amount can be limited. In other words, if the user initiates multiple identical purchases but completes none of them, the purchases are combined in a single series in which only the data for the first purchase is sent to the provider service. Once the last purchase in the series is completed and assigned the final status, the rest of the purchases in the series are declined and the platform sends callbacks with the 3613
response code. (For more information about the codes, see Operation statuses and response codes.)
By default, multiple purchases with the same amount are combined in a single series for 30 minutes after the user initiates the first purchase. Here an example of scenario of multiple purchases with the same amount:
- The user initiates the first purchase with amount of
500 THB
. The purchase data are sent to the provider service, and then the payment platform receives the data for redirecting the user to the provider service. The user does not complete the purchase. - The user initiates the second purchase with amount of
500 THB
. The purchase data are not sent to the provider service, and the payment platform redirects the user to the provider service by using the data the payment platform have received when initiating the first purchase. The user again does not complete the purchase. - The user initiates the third purchase with amount of
500 THB
. The purchase data are not sent to the provider service, and the payment platform redirects the user to the provider service by using the data the payment platform received when initiating the first purchase. The user completes the purchase. The purchase is assigned the final status, and the first and the second purchases are automatically rejected.
Once all the purchases are assigned their final statuses, the corresponding callbacks are sent to the web service.
Multiple purchases of the same user (with the same customer_id
) with the amount which differs from the amount of any of the previous purchases do not create any series, instead each purchase spawns a new queue. Here an example of scenario of multiple purchases with different amounts:
- The user initiates the first purchase with amount of
500 THB
. The purchase data are sent to the provider service, and then the payment platform receives the data for redirecting the user to the provider service. The user does not complete the first purchase. - The user initiates the second purchase with amount of
600 THB
. The purchase data are sent to the provider service, and then the payment platform receives the data for redirecting the user to the provider service. The user does not complete the second purchase. - The user initiates the third purchase with amount of
700 THB
. The purchase data are sent to the provider service, and then the payment platform receives the data for redirecting the user to the provider service. The user does not complete the third purchase. - The user initiates the fourth purchase with amount of
800 THB
. The purchase data are not sent to the provider service because of three-attempts limit. The payment platform receives the data for redirecting the user to the provider service which have been received when initiating the purchase for700 THB
.
Once the number of initiated purchases for different amounts (in which no amount is used twice) exceeds three, the user is redirected to the provider service with the redirection data of the last initiated purchase for unique amount. In our scenario, it is amount of 700 THB
.
Thus, a new user session won't start, unless one of purchases from the series is successfully completed or the current session times out. The user is confined by the 30-minutes limit and three redirections to the provider service.
Monetix reserves the right to change the time-out period and the allowed number of attempts and will notify of any changes of these limits in a separate message.
The sections that follow provide detailed information about what you need to perform payments and how you can analyze the information on payments and operations.
Purchase by using Payment Page
General information
In the Bank transfers in Thailand method, when processing a purchase by using Payment Page, the merchant web service should send a request with all the required parameters and signature to the Monetix URL and get the callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with the method selected. For more information about preselecting payment methods, see in Preselecting payment methods. The full sequence and particularities of the purchase process are provided below.
- A customer initiates a purchase on the merchant's web service.
- The web service sends the request for Payment Page opening to the specified Monetix URL.
- The request for opening is redirected to the payment platform.
- The payment platform performs the initial request processing that involves validation of the required parameters and signature.
- Requested Payment Page is generated into the Monetix payment platform as specified in the project settings and the request parameters.
- Payment Page is displayed to the customer.
- The customer selects the Bank transfers in Thailand method.
- The payment platform receives the purchase request for payment processing from Payment Page.
- The payment platform performs the internal purchase request processing and sends it to the provider service.
- The purchase request is processed on the provider service side.
- The provider service generates the data for redirecting the customer to its website form and sends it to the payment platform.
- The payment platform sends the customer redirection data to Payment Page.
- The customer is redirected to the provider website.
- The customer completes all the payment steps required.
- The payment is processed on the provider side.
- The result is displayed to the customer on the provider website.
- The customer is redirected to Payment Page.
- The provider service sends the result notification to the payment platform.
- The payment platform sends a callback with the payment result to the web service.
- The payment platform sends the result to Payment Page.
- A page with the payment result information is displayed to the customer on Payment Page.
The sections that follow discuss in more details the request format and the Payment Page parameters to use in the Bank transfers in Thailand payment method and provide the information on the format of callbacks with payment results. For the general information on how to use the API, see Payment Page API Description.
Request format
There are several things you need to consider when using the Bank transfers in Thailand method:
- You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
- project_id—project ID you obtained from Monetix
- payment_id—payment ID unique within the project
- customer_id—unique ID of the customer within your project
- customer_email—customer email
- customer_first_name—customer first name. If the parameter is missing from the request, Payment Page will contain an additional field for the customer to enter missing information. For more information about additional information submission, see in Submission of additional payment information.
- customer_last_name—customer last name. If the parameter is missing from the request, Payment Page will contain an additional field for the customer to enter missing information. For more information about additional information submission, see in Submission of additional payment information.
- payment_currency—payment currency in ISO-4217 alpha-3 format
- payment_amount—payment amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
- If you need to have payment form displayed with the Bank transfers in Thailand method selected, set the force_payment_method parameter to
bank-transfer-thailand
. - If required, you can also add any other additional parameters Payment Page supports.
- After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.
Here is an example of data from a request for Payment Page opening:
EPayWidget.run( { project_id: 1234, payment_id: 'payment_47', customer_id: 'customer_123', payment_amount: 30000, payment_currency: 'THB', customer_first_name: 'John', customer_last_name: 'Doe', customer_email: 'johndoe@email.com', signature: "kUi2x9dKHAVNU0FYldJrxhRLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg==" } )
For information about all parameters available in the Bank transfers in Thailand method, see Payment Page invocation parameters.
Callback format
The Bank transfers in Thailand method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks in Payment Page.
The following is the example of a callback with an information about successful 300.00 THB
purchase made in the 3514
project.
{ "project_id": 3514, "payment": { "id": "EP0c8a-960e", "type": "purchase", "status": "success", "date": "2021-02-10T10:10:14+0000", "method": "Thailand bank transfer", "sum": { "amount": 30000, "currency": "THB" }, "description": "" }, "operation": { "id": 360, "type": "sale", "status": "success", "date": "2021-02-10T10:10:14+0000", "created_date": "2021-02-10T10:09:34+0000", "request_id": "cca222750e99b05bc6656ec2d82df16cbb241a7-00000001", "sum_initial": { "amount": 30000, "currency": "THB" }, "sum_converted": { "amount": 30000, "currency": "THB" }, "code": "0", "message": "Success", "provider": { "id": 2885, "payment_id": "161295179796", "auth_code": "", "date": "2021-02-10T10:09:57+0000" } }, "signature": "9sHwkk4fbhwQg3PH/8ShWtbqgBZEcfaC+HnVrQe6DFFCQX14w==" }
The following is the example of a callback for a declined purchase.
{ "project_id": 3514, "payment": { "id": "EP20e2-f529", "type": "purchase", "status": "decline", "date": "2021-02-10T10:17:53+0000", "method": "Thailand bank transfer", "sum": { "amount": 35000, "currency": "THB" }, "description": "" }, "operation": { "id": 362, "type": "sale", "status": "decline", "date": "2021-02-10T10:17:53+0000", "created_date": "2021-02-10T10:17:20+0000", "request_id": "3c4c7fd62077fb13939f918db3ad68ac67b6-00000001", "sum_initial": { "amount": 35000, "currency": "THB" }, "sum_converted": { "amount": 35000, "currency": "THB" }, "code": "20000", "message": "General decline", "provider": { "id": 2885, "payment_id": "161295225928", "auth_code": "", "date": "2021-02-10T10:17:39+0000" } }, "signature": "OFk5zqGjZF7yAGjTdIY3vQs6i27N26bWHRM3hOBLgOg2n3pLoqTA==" }
Related topics
The following topics might be useful when implementing payments by using Payment Page:
Purchase by using Gate
General information
In the Bank transfers in Thailand method, when processing a purchase by using Gate, the merchant web service is required to do the following:
- Send a request with all the required parameters and signature to the Monetix URL.
- Perform the redirection of a customer to the provider service.
- Get the callback with the payment result from the payment platform.
The following diagram provides the detailed picture of the payment processing procedure.
- A customer initiates a purchase through Bank transfers in Thailand on the merchant's web service side.
- The web service sends the request for processing the purchase by using Gate to the specified Monetix URL.
- The payment platform receives the request for processing the purchase from Gate.
- The payment platform performs the initial request processing that includes validation of the required parameters and signature.
- The payment platform sends the response with request receipt confirmation and correctness check result to the web service. For more information, see Response structure.
- The payment platform performs the internal payment request processing and redirects the request to the provider service.
- The request is processed on the provider side.
- The provider service sends the data for redirecting the customer to the provider service to the payment platform.
- The payment platform sends the callback with the redirection data in the redirect_data object to the web service.
- The customer is redirected from the web service to the provider service.
- The customer completes all the payment steps required.
- The payment is processed on the provider side.
- The result is displayed to the customer.
- The customer is redirected to the merchant's web service.
- The provider service sends the payment result notification to the payment platform.
- The payment platform sends a callback to the web service.
- The customer receives the payment result on the web service.
The sections that follow discuss in more details the request format and the Gate parameters to use in the Bank transfers in Thailand payment method and provide the information on the format of callbacks with purchase results.
Request format
There are several things you must consider when using purchase requests in the Bank transfers in Thailand method:
- You perform purchases by sending the
/v2/payment/bank-transfer/thailand/sale
request by using POST (HTTP) method. This is a bank transferring request group: /v2/payment/bank-transfer/{payment_method}/sale - The following objects and parameters must be specified in any request:
- general—object with general request identification information:
- project_id—the project ID you obtained from Monetix
- payment_id—payment ID unique within the project
- signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
- customer—object with customer information:
- id—the unique ID of the customer within your project
- ip_address—customer device IP
- email—customer email
- first_name—customer first name
- last_name—customer last name
- payment—object with purchase information:
- amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
- currency—code of purchase currency in the ISO-4217 alpha-3 format
- return_url—object with URL(s) to return the customer to the web service:
- success—the URL to redirect the customer to after the payment is successfully completed
- general—object with general request identification information:
- The following parameters with the return URLs are optional, but we strongly advise you to specify them in the request to provide your customer a better user experience. If you don't specify any parameters of the return_url object in the request, by default Gate will redirect the customer to the URL specified in your project in Monetix.
- return_url—object with the information where to redirect the customer to when the payment is completed or prematurely terminated by the customer:
- decline—the URL to redirect the customer to after the payment is declined.
- return—the URL to redirect the customer to when they prematurely terminate the payment. This URL is also used if the success and decline parameters are not specified in the request.
- return_url—object with the information where to redirect the customer to when the payment is completed or prematurely terminated by the customer:
- If required, you can also add any other additional parameters Gate supports.
Here is an example of data from a purchase request in the Bank transfers in Thailand method.
{ "general": { "project_id": 1234, "payment_id": "payment_47", "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQsaC6tajQVVfBaNIipTv+AWoXW\/9MTO8yJA==" }, "payment": { "amount": 30000, "currency": "THB" }, "customer": { "id": "customer_123", "ip_address": "198.51.100.47", "first_name": "John", "last_name": "Doe", "email": "johndoe@example.com" }, "return_url": { "success": "https://example.com/success/", "decline": "https://example.com/decline/", "return": "https://example.com/return/" } }
Formats of the customer redirection data
After receiving and processing your purchase request, the payment platform sends a callback to your web service containing the data to redirect the customer to the provider service.
To redirect the customer, use the values of the following parameters in the redirect_data object:
- url—the URL to redirect the customer to
- body—the data to be sent in the request body
- method—the HTTP method to get an HTML page of the website (for example, POST or GET)
- encrypted—this is the service parameter. Ignore the data it contains.
Here is an example of a piece of callback containing the data to redirect the customer.
"redirect_data": { "method": "POST", "body": [], "encrypted": [], "url": "https://example.com/redirect" }
Callback format
The Bank transfers in Thailand method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks in Gate.
The following is the example of a callback with an information about successful 300.00 THB
purchase made in the 3514
project.
{ "project_id": 3514, "payment": { "id": "EP0c8a-960e", "type": "purchase", "status": "success", "date": "2021-02-10T10:10:14+0000", "method": "Thailand bank transfer", "sum": { "amount": 30000, "currency": "THB" }, "description": "" }, "operation": { "id": 360, "type": "sale", "status": "success", "date": "2021-02-10T10:10:14+0000", "created_date": "2021-02-10T10:09:34+0000", "request_id": "cca222750e99b05bc6656ec2d82df16cbb241a7-00000001", "sum_initial": { "amount": 30000, "currency": "THB" }, "sum_converted": { "amount": 30000, "currency": "THB" }, "code": "0", "message": "Success", "provider": { "id": 2885, "payment_id": "161295179796", "auth_code": "", "date": "2021-02-10T10:09:57+0000" } }, "signature": "9sHwkk4fbhwQg3PH/8ShWtbqgBZEcfaC+HnVrQe6DFFCQX14w==" }
The following is the example of a callback for a declined purchase.
{ "project_id": 3514, "payment": { "id": "EP20e2-f529", "type": "purchase", "status": "decline", "date": "2021-02-10T10:17:53+0000", "method": "Thailand bank transfer", "sum": { "amount": 35000, "currency": "THB" }, "description": "" }, "operation": { "id": 362, "type": "sale", "status": "decline", "date": "2021-02-10T10:17:53+0000", "created_date": "2021-02-10T10:17:20+0000", "request_id": "3c4c7fd62077fb13939f918db3ad68ac67b6-00000001", "sum_initial": { "amount": 35000, "currency": "THB" }, "sum_converted": { "amount": 35000, "currency": "THB" }, "code": "20000", "message": "General decline", "provider": { "id": 2885, "payment_id": "161295225928", "auth_code": "", "date": "2021-02-10T10:17:39+0000" } }, "signature": "OFk5zqGjZF7yAGjTdIY3vQs6i27N26bWHRM3hOBLgOg2n3pLoqTA==" }
Related topics
The following topics might be useful when implementing payments through Gate:
Analysis of payments results
As with other payment methods Monetix offers, when using this method, you have several options to analyze the information about payments and operations.
You can load and analyze all the necessary information in Dashboard (dash-light.trxhost.com
), for instance you can use the analytic panels in the Analytics section for this purpose.
Also, you can export the information for further analysis by using third party analytical tools. The following options are available:
- Dashboard allows you to download reports in CSV format by using the tools in the Reports section. You can perform export as a one-time or regular download of data to your local computer.
- Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by means of sending requests to the /operations/get endpoint.
If you have any further questions regarding payment data analysis, contact Monetix technical support.