OCBC Digital

Enable your customers to make payments using their OCBC Digital application right on mobile phone. Eliminating the need to enter their card details can help your customers checkout faster.

This guide walks you through the payment flow and details on how to implement.

The customer is required to have a mobile application OCBC Digital.

How to enable

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

To enable OCBC Digital, 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 Mobile Banking go through an app_redirect payment flow. This means they are redirected from your website or mobile application to the corresponding Bank's mobile application where they authorize and confirm the payment.

After the customer selects OCBC Digital as their preferred payment method, your site should redirect the customer to the OCBC Digital application by using the resulting URI (a “deep link” that will automatically open the installed handler app). The following screenshots demonstrate completing the payment flow using a mobile browser. The customer must pay via OCBC Digital to complete the payment.

Using a mobile browser

❶ The customer chooses OCBC Digital to pay with. ❷ They will be redirected to the OCBC Digital application to confirm the payment. ❸ The payment details are shown, then they confirm the payment. ❹ The payment confirmation page is shown ❺ After the payment is completed, the customer will be redirected to the merchant's confirmation details page automatically.

Implementation

To create a charge using OCBC Digital, make the following API requests.

1. Create a new payment source (type: mobile_banking_ocbc) 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 OCBC Digital source on the client (a customer's browser or mobile phone). Use your secret key to create the OCBC Digital 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, platform_type, and type.

The following examples demonstrate the creation of a new OCBC Digital source for S$1500. 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('mobile_banking_ocbc', {
  "amount": 150000,
  "currency": "SGD",
  "platform_type": "IOS"
}, 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=150000" \
  -d "currency=SGD" \
  -d "type=mobile_banking_ocbc" \
  -d "platform_type=IOS"

{
  "object": "source",
  "id": "src_test_5wzvaruxsnu52w9m07q",
  "livemode": false,
  "location": "/sources/src_test_5wzvaruxsnu52w9m07q",
  "amount": 150000,
  "barcode": null,
  "bank": null,
  "created_at": "2023-09-04T07:04:00Z",
  "currency": "SGD",
  "email": null,
  "flow": "app_redirect",
  "installment_term": null,
  "ip": null,
  "absorption_type": null,
  "name": null,
  "mobile_number": null,
  "phone_number": null,
  "platform_type": "IOS",
  "scannable_code": null,
  "billing": null,
  "shipping": null,
  "items": [],
  "references": null,
  "provider_references": null,
  "store_id": null,
  "store_name": null,
  "terminal_id": null,
  "type": "mobile_banking_ocbc",
  "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.
• 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=150000" \
  -d "currency=SGD" \
  -d "return_uri=http://example.com/orders/345678/complete" \
  -d "source=$SOURCE_ID"

{
  "object": "charge",
  "id": "chrg_test_5wzvary0efxnie96mgi",
  "location": "/charges/chrg_test_5wzvary0efxnie96mgi",
  "amount": 150000,
  "net": 148500,
  "fee": 1500,
  "fee_vat": 0,
  "interest": 0,
  "interest_vat": 0,
  "funding_amount": 150000,
  "refunded_amount": 0,
  "transaction_fees": {
    "fee_flat": "0.0",
    "fee_rate": "1.0",
    "vat_rate": "0.0"
  },
  "platform_fee": {
    "fixed": null,
    "amount": null,
    "percentage": null
  },
  "currency": "SGD",
  "funding_currency": "SGD",
  "ip": null,
  "refunds": {
    "object": "list",
    "data": [],
    "limit": 20,
    "offset": 0,
    "total": 0,
    "location": "/charges/chrg_test_5wzvary0efxnie96mgi/refunds",
    "order": "chronological",
    "from": "1970-01-01T00:00:00Z",
    "to": "2023-09-04T07:04:01Z"
  },
  "link": null,
  "description": null,
  "metadata": {},
  "card": null,
  "source": {
    "object": "source",
    "id": "src_test_5wzvarmtp15fm7jcp4m",
    "livemode": false,
    "location": "/sources/src_test_5wzvarmtp15fm7jcp4m",
    "amount": 150000,
    "barcode": null,
    "bank": null,
    "created_at": "2023-09-04T07:03:59Z",
    "currency": "SGD",
    "email": null,
    "flow": "app_redirect",
    "installment_term": null,
    "ip": null,
    "absorption_type": null,
    "name": null,
    "mobile_number": null,
    "phone_number": null,
    "platform_type": "IOS",
    "scannable_code": null,
    "billing": null,
    "shipping": null,
    "items": [],
    "references": null,
    "provider_references": null,
    "store_id": null,
    "store_name": null,
    "terminal_id": null,
    "type": "mobile_banking_ocbc",
    "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/payments/pay2_test_5wzvary1qagtsne8oq1/authorize",
  "return_uri": "http://example.com/orders/345678/complete",
  "created_at": "2023-09-04T07:04:01Z",
  "paid_at": null,
  "expires_at": "2023-09-11T07:04:01Z",
  "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": false,
  "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=150000" \
  -d "currency=SGD" \
  -d "return_uri=http://example.com/orders/345678/complete" \
  -d "source[type]=mobile_banking_ocbc" \
  -d "source[platform_type]=IOS"

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.

Authorizing the charge

Redirect the customer to location specified in authorize_uri so that 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 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.

Refunds

OCBC Digital charges can be partially or fully refunded within 180 days of the transaction date through our refund API or the charge page on your dashboard.

Limits

• Minimum: 100 (SGD1.00)
• Maximum: 2000000 (SGD20,000.00)

Next steps

• Charge API
• Source API
• Webhooks API