Introduction

BIEASES payment gateway is a service provided to merchants who can integrate BIEASES as a new payment method on their economy platform or other order system. BIEASES payment gateway can be integrated simply with one API.

How is the BIEASES payment gateway working?

Check below the diagram to find out how the BIEASES payment gateway works with End User/Merchant and BIEASES.

Integration Steps

Please follow the steps below to complete the BIEASES payment gateway integration flow.

  1. Follow up on the Quick Start to Sign Up and complete the KYB.
  2. Request sandbox access to create a sandbox and get sandbox secure keys.
  3. The customer completes the development and testing in the sandbox environment.
  4. Once the development and testing are done, contact [email protected] or your account manager to request production secure keys.
  5. Go live.

Setup Environment

Generate keys

BIEASES will generate and give the sign / encryption keys. Please contact your account manager or [email protected] to get your Keys generated once you completed the onboarding process.

🚧

Note:

Keep the private key securely, and do not share it with anyone else.

Sandbox

📘

Prerequisites:

  • Has a valid BIEASES merchant account (follow the Quick Start to create a merchant account).

Request sandbox access

Merchants use the BIEASES payment gateway sandbox to develop and test their integration with BIEASES.

Only merchant users can have sandbox environment access. Please send a request to [email protected] with your merchant ID to obtain the sandbox environment access and the secure keys.

The secure keys include:

Key TypeDescription
RSA key pairsUse to sign and verify the signature. Including the public key and private key.
AES keyUse to encrypt/decrypt the payment order information.
IV stringA unique, random, and non-repeating value used in cryptography to add randomization to the encryption process.

Each key is bound to the merchant ID.

🚧

Note:

Currently, the sandbox can only be accessed via a website. Mobile apps are not supported.

Endpoints and Login Portal

For the EEA/UK Region:

Production

📘

Prerequisites:

  • Has completed the development and testing in a sandbox environment.

Request production secure keys

Once the merchant completed the development and testing in the sandbox. Contact [email protected] to issue the production secure keys.

The secure keys including:


Key TypeDescription
RSA key pairsUse to sign and verify the signature. Including the public key and private key.
AES keyUse to encrypt/decrypt the payment order information.
IV stringA unique, random, and non-repeating value used in cryptography to add randomization to the encryption process.

🚧

Note:

  1. Please keep the production secure keys safe and do not share those keys with anyone else.
  2. Please contact [email protected] to re-issue the keys if the key was lost.

Production Endpoint(s)

Replace the sandbox base URL with the production URL while deploying to the merchant production environment.

For the EEA/UKRegion:

📘

Note:

All the HTTP requests require TLS 1.2 or higher.

Whitelist server IP address

Before going live, the merchant back-end server IP address(es) needs to be whitelisted. Please contact [email protected] to add your back-end server IP address to the whitelist or remediate the IP whitelist.