Bank transfers in Laos - Purchase

When performing a purchase, the customer follows the payment instructions displayed on the checkout page or in your system (when performing the purchase by using Gate).


Countries and regions	Lao People's Democratic Republic
Payment currencies	LAK
Payment amount limits	Contact your key account manager at Monetix for details. Also you can check the payment amount limits in your project by using Dashboard.
Payment processing time	Contact your key account manager at Monetix for details.
Currency conversion	On the Monetix side
Refund
Onboarding and access fee	Contact your key account manager at Monetix for details.
Special considerations If the customer makes a transfer for an incorrect payment amount, the payment will be declined.

Operations support


	Interfaces
	Payment Page	Gate	Dashboard
Purchase

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 then click the Payment methods tab.

The following sections provide more information about the payment processing flow and the analysis of completed payments.

Supported banks

Payments through the Bank transfers in Laos method are carried out through the banks that support the method. To initiate purchases by using Gate, you use bank identifiers which are also used to display banks on Payment Page where your customer can choose a payment method.

The tables below provide information about supported banks.

Table 1. List of banks
Bank	ID
BCEL	60881

Purchase by using Payment Page

General information

To perform a purchase by using Payment Page with the Bank transfers in Laos payment method:

Send a request with all the required parameters and signature to the Monetix URL.
Accept the callback with the purchase result from the payment platform.

The following figure shows the complete purchase processing flow in the Bank transfers in Laos payment method.

Figure 1. Purchase processing steps for a purchase by using Payment Page

The customer initiates a purchase in your system.
Your system sends the request for the purchase through Payment Page to the Monetix URL.
The checkout page is displayed to the customer.
The customer chooses to make a purchase with the Bank transfers in Laos payment method.
The payment platform forwards the request to the provider service.
The provider service generates the payment instructions to show to the customer and sends them to the payment platform.
The checkout page displays the payment instructions to the customer.
The customer completes the purchase.
The provider service sends the purchase result information to the payment platform.
The payment platform sends a callback with the payment result to your system.
The payment platform displays the payment result to the customer on the checkout page.

Request

The following table lists the parameters that you need to include in the request for purchase through the checkout page with the Bank transfers in Laos payment method.

strictly required—the parameter must be in the initial request.

required—the parameter is required for purchase processing but using it in the initial request is optional. If you don't specify this parameter in your request, the checkout page will contain an additional field for the customer to enter the missing information. For more information on how to act in such cases, see Submission of additional payment information.

optional—the parameter is optional but adding it to the request either makes the payment process more customer-friendly or helps to increase the percentage of successful payments.

Parameter Description

project_id
integer
strictly required

Project ID you obtained from Monetix when integrating.

Example: 1234

payment_id
string
strictly required

Payment ID unique within your project.

Example: payment_47

customer_id
string
strictly required

Unique ID of the customer within your project.

Example: customer_123

customer_email
string
strictly required

Customer's email.

Example: johndoe@example.com

account_customer_name
string
required

Customer's full name.

Example: John Doe

payment_currency
string
strictly required

Code of the payment currency in the ISO-4217 alpha-3 format.

Example: LAK

payment_amount
integer
strictly required

Payment amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units.

If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 500,000.00 LAK must be sent as 50000000

force_payment_method
string
optional

Parameter that allows you to enforce the Bank transfers in Laos payment method for your customer and skip the page with payment method selections.

To enforce the Bank transfers in Laos payment method and skip the page with payment method selection, add the force_payment_method parameter to the request and set its value to bank-transfer-laos. For more information about enforcing payment methods, see Preselecting payment methods.

Example: force_payment_method: 'bank-transfer-laos'

signature
string
strictly required

Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.

language_code
string
optional

The language code of the payment results message. By default, these messages are displayed in Lao language. To change the language to English, set this parameter to en.

Example: en

You can also add any other optional parameters to the request, if necessary. For the list of all the parameters possible in requests to Payment Page, see Payment Page invocation parameters.

Here is an example of the data from a request to open the checkout page by using EPayWidget:

EPayWidget.run(
	{
		project_id: 1234,
		payment_id: 'payment_47',
		customer_id: 'customer_123',
		customer_email: 'johndoe@example.com',
		account_customer_name: 'John Doe',
		payment_currency: 'LAK',
		payment_amount: 50000000,
		force_payment_method: 'bank-transfer-laos',
		signature: 'kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO/RLUkDJrOcZzUCwX6R/ekpZhkIQg==',
		language_code: 'en'
	}
)

Callback

In the Bank transfers in Laos payment method, the payment platform returns the purchase result in a callback. For the information about the callback structure, see Callbacks in Payment Page.

The following is an example of a callback body with information about a successfully completed purchase.

Figure 2. Example of the data from a successful purchase callback

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "method": "bank-transfer/laos",
        "sum": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "sum_converted": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is an example of a callback for a declined purchase.

Figure 3. Example of the data from a declined purchase callback

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "method": "bank-transfer/laos",
        "sum": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "sum_converted": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

Purchase by using Gate

General information

To perform a purchase by using Gate with the Bank transfers in Laos payment method:

Send a request with all the required parameters and signature to the Monetix URL.
Show the screen with payment instructions to the customer.
Accept the callback with the purchase result from the payment platform.

The following figure provides the details of the purchase processing flow in the Bank transfers in Laos payment method.

Figure 4. Purchase processing flow when performing a purchase by using Gate

The customer initiates a purchase in your system.
Your system sends the purchase request to the Monetix payment platform.
The payment platform sends you a response in which it acknowledges your request and provides the request validation result. (For more information about the response format, see Response structure.)
The payment platform processes the request and forwards it to the provider service.
The provider service generates the payment instructions to show to the customer and sends them to the payment platform.
The payment platform forwards the instructions to your system in the display_data array.
Your system displays the payment instructions to the customer.
The customer completes the purchase.
The provider service informs the payment platform about the purchase result.
The payment platform sends the callback with the payment result to your system.
Your system sends the payment result to the customer.

Request

This section provides the instructions on how to build the request for purchase with the Bank transfers in Laos payment method.


HTTP request method	POST
Request body format	JSON
API endpoint	`/v2/payment/bank-transfer/laos/sale`
Full API endpoint specification	/v2/payment/bank-transfer/{payment_method}/sale

strictly required—the parameter must be in the initial request.

required—the parameter is required for purchase processing but using it in the initial request is optional. If you omit this parameter from the request, the payment platform will request the parameter by sending your system a callback with the list of all the missing parameters you are required to submit. For more information on how to act in such cases, see Submission of additional payment information.

Object Parameter Description

general
object
strictly required

project_id
integer
strictly required

Project ID you obtained from Monetix when integrating.

Example: 1234

payment_id
string
strictly required

Payment ID unique within your project.

Example: payment_47

signature
string
strictly required

Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.

customer
object
strictly required

id
string
strictly required

Unique ID of the customer within your project.

Example: customer_123

ip_address
string
strictly required

IP address of the customer's device.

Example: 198.51.100.47

email
string
strictly required

Customer's email.

Example: johndoe@example.com

account
object
required

customer_name
string
required

Customer's full name.

Example: John Doe

payment
object
strictly required

currency
string
strictly required

Code of the payment currency in the ISO-4217 alpha-3 format.

Example: LAK

amount
integer
strictly required

Payment amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units.

Example: 500,000.00 LAK must be sent as 50000000

You can also add any other optional parameters to the purchase request, if necessary. For the list of all the parameters available in Gate, see API Reference.

Here is an example of the data from a request to initiate a purchase with the Bank transfers in Laos payment method:

Figure 5. Example of the purchase request body

{
    "general": {
        "project_id": 1234,
        "payment_id": "payment_47",
        "signature": "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO/RLUkDJrOcZzUCwX6R/ekpZhkIQg=="
    },
    "customer": {
        "id": "customer_123",
        "ip_address": "198.51.100.47",
        "email": "johndoe@example.com"
    },
    "account": {
        "customer_name": "John Doe"
    },
    "payment": {
        "currency": "LAK",
        "amount": 50000000
    }
}

Format of the data for displaying the payment instructions

After receiving and processing your purchase request, the payment platform sends you the callback with the data for displaying the payment instructions to the customer.

Use the data from the display_data array to display the payment instructions to the customer.

Table 4. Description of the display_data array
Element	Description
`{ "type": "add_info", "title": "invoice_number", "data": "12345678901234" }`	Operation number. This element is always presented in display_data array. Example: `12345678901234`
`{ "type": "add_info", "title": "payment_amount_show", "data": "500000.00" }`	Payment amount to show in the payment instructions. This element is always presented in display_data array. Example: `500000.00`
`{ "type": "add_info", "title": "bank_code", "data": "BCEL" }`	Bank code. This element is always presented in display_data array. Example: `BCEL`
`{ "type": "add_info", "title": "account_number", "data": "123 456 789" }`	Payment recipient account. This element is always presented in display_data array. Example: `123 456 789`
`{ "type": "add_info", "title": "bank_name", "data": "BCEL" }`	Bank name. This element is always presented in display_data array. Example: `BCEL`
`{ "type": "qr_url", "title": "qr_url", "data": "https://example.com/qr.png" }`	The link to display the QR code. This parameter may be not presented in the display_data array. Contact your key account manager at Monetix to find out if this element will be displayed to your customer. Example: `https://example.com/qr.png`

The following is a sample callback snippet with the display_data array.

"display_data": [
	{
		"type": "add_info",
		"title": "invoice_number",
		"data": "12345678901234"
	},
	{
		"type": "add_info",
		"title": "payment_amount_show",
		"data": "500000.00" 
	},
	{
		"type": "add_info",
		"title": "bank_code",
		"data": "BCEL"
	},
	{
		"type": "add_info",
		"title": "account_number",
		"data": "123 456 789"
	},
	{
		"type": "add_info",
		"title": "bank_name",
		"data": "BCEL"
	},
	{
		"type": "qr_url",
		"title": "qr_url",
		"data": "https://example.com/qr.png "
	}
]

Callback

In the Bank transfers in Laos payment method, the payment platform returns the purchase result in a callback. For the information about the callback structure, see Callbacks in Gate.

The following is an example of a callback body with the information about a successfully completed purchase.

Figure 6. Example of the data from a successful purchase callback

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "method": "bank-transfer/laos",
        "sum": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "success",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "sum_converted": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is an example of a callback for a declined purchase.

Figure 7. Example of the data from a declined purchase callback

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "method": "bank-transfer/laos",
        "sum": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 47,
        "type": "sale",
        "status": "decline",
        "date": "2024-12-07T19:08:45+0000",
        "created_date": "2024-12-07T19:08:05+0000",
        "request_id": "1a23456bc7890de",
        "sum_initial": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "sum_converted": {
            "amount": 50000000,
            "currency": "LAK"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4XrUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

Bank transfers in Laos - Purchase

Operations support

Supported banks

Purchase by using Payment Page

General information

Request

Callback

Related topics

Purchase by using Gate

General information

Request

Format of the data for displaying the payment instructions

Callback

Related topics