Bill Payment

Topics covered on this page

Please be informed that the bill payment service will be discontinued on Oct 1st, 2024. Merchants can continue to use other payment methods as usual. We apologize for any inconvenience this may cause.

Enable your customers to pay for purchases over the counter using Bill Payment. This payment method generates a unique barcode at checkout which your customer can take to supported Lotus's branches to pay at their convenience. This guide walks you through the payment flow and details on how to implement.

Lotus's charges a transaction fee of ฿10 to the customer at the payment point.

How to enable

  • Supported Countries: Thailand
  • Minimum API version: 2017-11-02

To enable Bill Payment, send an email requesting this feature to support@opn.ooo. You will need to review and accept new terms and conditions.

Payment flow

Customers paying via Bill Payment go through an offline payment flow. This means that once the charge is created, it must be authorized by the customer at a physical location.

The following screenshots illustrate this flow. First, the customer selects the payment method Lotus's Bill Payment.

Bill payment flow

This creates a unique barcode which the customer can present at a Lotus's payment counter to complete the charge. The barcode will expire in 24 hours.

Upon payment, Opnn Payments will send a webhook event (if enabled) indicating that the charge is complete.

Bill payment flow 2

Implementation

To create a charge using Bill Payment, make the following API requests.

  1. Create a new payment source (type: bill_payment_tesco_lotus) using Omise.js or one of the mobile SDKs (iOS and Android)
  2. Create a new charge using the identifier of the source created in Step 1.
  3. After receiving the charge completion webhook event, retrieve the charge to verify its status (optional, but recommended).

Use your public key to create the Bill Payment source on the client (a customer's browser or mobile phone). Use your secret key to create the Bill Payment 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 Bill Payment source for ฿4,000. Replace the omise_public_key and $OMISE_PUBLIC_KEY variables with the test public key found on your dashboard.

Using Omise.js, the type parameter is supplied as the first argument to the createSource method.

Omise.setPublicKey(omise_public_key);

Omise.createSource('bill_payment_tesco_lotus', {
  "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=bill_payment_tesco_lotus"
{
  "object": "source",
  "id": "src_test_5lwtu0n9gbcrne0p622",
  "livemode": false,
  "location": "/sources/src_test_5lwtu0n9gbcrne0p622",
  "amount": 400000,
  "barcode": null,
  "created_at": "2020-11-18T01:47:38Z",
  "currency": "THB",
  "email": null,
  "flow": "offline",
  "installment_term": null,
  "name": null,
  "mobile_number": null,
  "phone_number": null,
  "scannable_code": null,
  "references": null,
  "store_id": null,
  "store_name": null,
  "terminal_id": null,
  "type": "bill_payment_tesco_lotus",
  "zero_interest_installments": null,
  "charge_status": "unknown"
}

The id attribute is the source identifier (begins with src).

Creating a charge

Create a charge specifying the parameters source, amount, and currency.

  • source specifies the source identifier.
  • amount and currency must match amount and currency of the source.

The following example demonstrates how to create a new charge using curl. Replace $OMISE_SECRET_KEY with your test secret key found 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 "source=$SOURCE_ID"
{
  "object": "charge",
  "id": "chrg_test_5lwtu0sb5oziy7m1oy5",
  "location": "/charges/chrg_test_5lwtu0sb5oziy7m1oy5",
  "amount": 400000,
  "net": 384378,
  "fee": 14600,
  "fee_vat": 1022,
  "interest": 0,
  "interest_vat": 0,
  "funding_amount": 400000,
  "refunded_amount": 0,
  "authorized": false,
  "capturable": false,
  "capture": true,
  "disputable": false,
  "livemode": false,
  "refundable": false,
  "reversed": false,
  "reversible": false,
  "voided": false,
  "paid": false,
  "expired": false,
  "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_test_5lwtu0sb5oziy7m1oy5/refunds",
    "order": "chronological",
    "from": "1970-01-01T00:00:00Z",
    "to": "2020-11-18T01:47:39Z"
  },
  "link": null,
  "description": null,
  "metadata": {},
  "card": null,
  "source": {
    "object": "source",
    "id": "src_test_5lwtu0bpmwp4n3i9ylf",
    "livemode": false,
    "location": "/sources/src_test_5lwtu0bpmwp4n3i9ylf",
    "amount": 400000,
    "barcode": null,
    "created_at": "2020-11-18T01:47:36Z",
    "currency": "THB",
    "email": null,
    "flow": "offline",
    "installment_term": null,
    "name": null,
    "mobile_number": null,
    "phone_number": null,
    "scannable_code": null,
    "references": {
      "expires_at": "2020-11-19T01:47:38Z",
      "device_id": null,
      "customer_amount": null,
      "customer_currency": null,
      "customer_exchange_rate": null,
      "omise_tax_id": "0105556091152",
      "reference_number_1": "707143688374935790",
      "reference_number_2": "300256148058569221",
      "barcode": "https://api.omise.co/charges/chrg_test_5lwtu0sb5oziy7m1oy5/documents/docu_test_5lwtu0tm9ujmfggobgh/downloads/9D514896BA3DB0CE",
      "payment_code": null,
      "va_code": null
    },
    "store_id": null,
    "store_name": null,
    "terminal_id": null,
    "type": "bill_payment_tesco_lotus",
    "zero_interest_installments": null,
    "charge_status": "pending"
  },
  "schedule": null,
  "customer": null,
  "dispute": null,
  "transaction": null,
  "failure_code": null,
  "failure_message": null,
  "status": "pending",
  "authorize_uri": null,
  "return_uri": null,
  "created_at": "2020-11-18T01:47:38Z",
  "paid_at": null,
  "expires_at": "2020-11-19T01:47:38Z",
  "expired_at": null,
  "reversed_at": null,
  "zero_interest_installments": true,
  "branch": null,
  "terminal": null,
  "device": null
}

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 "source[type]=bill_payment_tesco_lotus"

Completing the charge

At this point, 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.

sequenceDiagram participant customer participant omise.js participant merchant participant api.omise.co participant offline provider customer->>omise.js: Send payment details for purchase omise.js->>api.omise.co: Request source using payment details api.omise.co-->>omise.js: Return source omise.js->>merchant: Merchant gets returned source merchant->>api.omise.co: Request charge using source and purchase details api.omise.co-xmerchant: Send "charge.create" webhook api.omise.co-->>merchant: Return charge customer->>offline provider: Provide payment or charge authorization at offline provider offline provider-->>api.omise.co: Return result of payment or charge authorization api.omise.co-xmerchant: Send "charge.complete" webhook merchant-xcustomer: Send charge result (e.g. via email)

Authorizing the charge

Present the customer with barcode generated at charge creation. To authorize the charge, the customer presents the barcode at a Lotus's payment counter.

Find the barcode (and associated information) nested within the charge object as follows:

charge:
  source:
    references:
      barcode: Barcode image to present to the customer (SVG)
      expires_at: Charge expiration date.
      omise_tax_id: Omise Tax ID, present with barcode.
      reference_number_1: Present with barcode.
      reference_number_2: Present with barcode.

Present the barcode in accordance with the Thailand Payment Barcode Standard. The height of the barcode must be no less than 1 centimeter. Below the barcode, present the payment information encoded within the barcode in the following format (including the leading pipe (|) character and the 00):

| omise_tax_id 00 reference_number_1 reference_number_2 charge.amount
{
  "expires_at": "2020-11-19T01:47:36Z",
  "device_id": null,
  "customer_amount": null,
  "customer_currency": null,
  "customer_exchange_rate": null,
  "omise_tax_id": "0105556091152",
  "reference_number_1": "835847145569308915",
  "reference_number_2": "351521093929347035",
  "barcode": "https://api.omise.co/charges/chrg_test_5lwtu0f0z15knfih9ax/documents/docu_test_5lwtu0g1oneoxyxesee/downloads/4E74776F9AC23FA6",
  "payment_code": null,
  "va_code": null
}

Receiving the charge completion event

The best way for you to be notified of the completion of a charge is 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 will be sent to this endpoint with the charge response embedded.

The key attribute for the event object contains charge.complete and the data attribute contains the charge object. See Events API for 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
timeout Payer did not take action before charge expiration.

Voids and refunds

Bill Payment charges cannot be voided or refunded through Opn Payments. Please contact Lotus's customer service.

Limits

  • Minimum: 2000 (THB20.00)
  • Maximum: 4900000 (THB49,000.00)

Next steps

Omise uses cookies to improve your overall site experience and collect information on your visits and browsing behavior. By continuing to browse our website, you agree to our Privacy Policy. Learn more