Thai Internet Banking
Topics covered on this page
Enable customers to purchase directly from their bank accounts using Internet Banking. This guide walks you through the payment flow and details how to implement it.
To accept Internet banking payments with a merchant account registered in Japan, see Konbini, Pay-easy, Online Banking.
How to enable
- Supported Countries: Thailand
- Minimum API version:
2014-07-27
To enable Internet Banking, send an email requesting this feature to support@omise.co. You will need to review and accept new terms and conditions.
See a previous version of this guide for instructions on how to implement this feature for API versions before
2017-11-02
.
Supported banks
Bank | Service | Source type |
---|---|---|
Bank of Ayudhya (Krungsri) | Krungsri Online | internet_banking_bay |
Bangkok Bank | Bualuang iBanking | internet_banking_bbl |
Payment flow
Customers paying via Internet Banking go through a redirect payment flow. They are redirected from your website to authorize and confirm the charge. Upon completion, the customer is redirected back to your website.
The following screenshots demonstrate this flow.
First, the customer selects Internet Banking
as their preferred payment method.
After choosing the bank, the customer is redirected to the external page operated by the bank.
The payment details confirm the payment; the customer is redirected to your website via the specified return URL. Omise will send a webhook event (if enabled) indicating that the charge is complete.
Implementation
To create a charge using Internet Banking, make the following API requests.
- Create a new payment source (
type
:internet_banking_bay
, orinternet_banking_bbl
) using Omise.js or one of the mobile SDKs (iOS and Android) - Create a new charge using the identifier of the source created in Step 1.
- After receiving the charge completion webhook event, retrieve the charge to verify its status (optional, but recommended).
Use your public key to create the Internet Banking source on the client (a customer's browser or mobile phone). Use your secret key to create the Internet Banking charge on the server.
If both the creation and charge of a source must happen server-side, you can create and charge the source in a single API request using your secret key.
Creating a source
When the customer confirms that they wish to pay with this payment method, create a new source specifying the amount
, currency
, and type
.
The following examples demonstrate the creation of a new Internet Banking source for ฿4,000. Replace the omise_public_key
and $OMISE_PUBLIC_KEY
variables with the test public key on your dashboard.
Using Omise.js, the
type
parameter is supplied as the first argument to thecreateSource
method.
Omise.setPublicKey(omise_public_key);
Omise.createSource('internet_banking_bay', {
"amount": 400000,
"currency": "THB"
}, function(statusCode, response) {
console.log(response)
});
For testing, you can create the same request using curl.
curl https://api.omise.co/sources \
-u $OMISE_PUBLIC_KEY: \
-d "amount=400000" \
-d "currency=THB" \
-d "type=internet_banking_bay"
{
"object": "source",
"id": "src_5uvjauky26c4og5oyf8",
"livemode": true,
"location": "/sources/src_5uvjauky26c4og5oyf8",
"amount": 400000,
"barcode": null,
"bank": null,
"created_at": "2023-02-21T03:13:52Z",
"currency": "THB",
"email": null,
"flow": "redirect",
"installment_term": null,
"absorption_type": null,
"name": null,
"mobile_number": null,
"phone_number": null,
"platform_type": null,
"scannable_code": null,
"billing": null,
"shipping": null,
"items": [],
"references": null,
"store_id": null,
"store_name": null,
"terminal_id": null,
"type": "internet_banking_bay",
"zero_interest_installments": null,
"charge_status": "unknown",
"receipt_amount": null,
"discounts": []
}
The id
attribute is the source identifier (begins with src
).
Creating a charge
Create a charge specifying the parameters return_uri
, source
, amount
, and currency
.
return_uri
specifies the location on your website to which the customer should be redirected after completing the payment authorization step.source
specifies the source identifier.- The
amount
andcurrency
must match those of the source.
The following example demonstrates how to create a new charge using curl.
Replace $OMISE_SECRET_KEY
with the test secret key on your dashboard.
Replace $SOURCE_ID
with the id
of the source.
curl https://api.omise.co/charges \
-u $OMISE_SECRET_KEY: \
-d "amount=400000" \
-d "currency=THB" \
-d "return_uri=https://example.com/orders/345678/complete" \
-d "source=$SOURCE_ID"
{
"object": "charge",
"id": "chrg_5uvjauo4i23ibyyz39u",
"location": "/charges/chrg_5uvjauo4i23ibyyz39u",
"amount": 400000,
"net": 384378,
"fee": 14600,
"fee_vat": 1022,
"interest": 0,
"interest_vat": 0,
"funding_amount": 400000,
"refunded_amount": 0,
"transaction_fees": {
"fee_flat": "0.0",
"fee_rate": "3.65",
"vat_rate": "7.0"
},
"platform_fee": {
"fixed": null,
"amount": null,
"percentage": null
},
"currency": "THB",
"funding_currency": "THB",
"ip": null,
"refunds": {
"object": "list",
"data": [],
"limit": 20,
"offset": 0,
"total": 0,
"location": "/charges/chrg_5uvjauo4i23ibyyz39u/refunds",
"order": "chronological",
"from": "1970-01-01T00:00:00Z",
"to": "2023-02-21T03:13:53Z"
},
"link": null,
"description": null,
"metadata": {},
"card": null,
"source": {
"object": "source",
"id": "src_5uvjaubfmq3w51k2fnu",
"livemode": true,
"location": "/sources/src_5uvjaubfmq3w51k2fnu",
"amount": 400000,
"barcode": null,
"bank": null,
"created_at": "2023-02-21T03:13:51Z",
"currency": "THB",
"email": null,
"flow": "redirect",
"installment_term": null,
"absorption_type": null,
"name": null,
"mobile_number": null,
"phone_number": null,
"platform_type": null,
"scannable_code": null,
"billing": null,
"shipping": null,
"items": [],
"references": null,
"store_id": null,
"store_name": null,
"terminal_id": null,
"type": "internet_banking_bay",
"zero_interest_installments": null,
"charge_status": "pending",
"receipt_amount": null,
"discounts": []
},
"schedule": null,
"customer": null,
"dispute": null,
"transaction": null,
"failure_code": null,
"failure_message": null,
"status": "pending",
"authorize_uri": "https://pay.omise.co/offsites/ofsp_5uvjauo6dtoqkmgmhvg/pay",
"return_uri": "https://example.com/orders/345678/complete",
"created_at": "2023-02-21T03:13:53Z",
"paid_at": null,
"expires_at": "2023-02-28T03:13:53Z",
"expired_at": null,
"reversed_at": null,
"zero_interest_installments": false,
"branch": null,
"terminal": null,
"device": null,
"authorized": false,
"capturable": false,
"capture": true,
"disputable": false,
"livemode": true,
"refundable": false,
"reversed": false,
"reversible": false,
"voided": false,
"paid": false,
"expired": false
}
Creating a source and charge
Alternatively, you can create and charge a source in a single API request.
curl https://api.omise.co/charges \
-u $OMISE_SECRET_KEY: \
-d "amount=400000" \
-d "currency=THB" \
-d "return_uri=http://example.com/orders/345678/complete" \
-d "source[type]=internet_banking_bay"
Completing the charge
You have created a new charge with its status
set to pending
.
Other possible values for charge status
are successful
, failed
, and expired
.
The following sections detail how to authorize a charge, receive its completion webhook event, and update its status.
This sequence diagram shows the entire flow.
Authorizing the charge
Redirect the customer to the location specified in authorize_uri
so they can authorize the charge.
You can simulate this authorization phase in test mode by visiting the authorize_uri
to manually mark the charge as Successful
or Failed
.
After the customer has completed the authorization phase, they will be redirected to the location you specified in return_uri
.
Receiving the charge completion event
The best way to be notified of a charge completion is by using webhook events. Set up a location on your server to receive webhook events, and add this location as a webhook endpoint on the dashboard.
Once a charge is completed, a POST request with the charge response embedded will be sent to this endpoint.
The key
attribute for the event object contains charge.complete
, and the data
attribute contains the charge object.
See Events API for the event object structure.
Checking the charge status
After receiving this event, retrieve the charge using its id
and confirm that its status
matches the status
of the charge contained in the event.
If the value of status
is successful
, you got paid.
If the value of status
is failed
, check the failure_code
and failure_message
in the charge object for an explanation.
Possible failure codes are listed below.
Failure Code | Description |
---|---|
failed_processing |
General payment processing failure. |
insufficient_balance |
Insufficient funds in the account or the payment method has reached its limit. |
payment_cancelled |
Payment canceled by the payer. |
timeout |
Payer did not take action before charge expiration. |
Voids and refunds
Internet Banking charges cannot be voided or refunded through Omise.
Limits
- Minimum:
2000
(THB20.00) - Maximum:
15000000
(THB150,000.00)