Payment-method icon

Atome for API only

Add Atome to an existing API-only integration.

Accept Atome payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Requirements

Requirement Description
Integration type Make sure that you have an existing API-only integration.
Setup steps Before you begin, contact our Support Team to add Atome in your Customer Area.

Build your payment form for Atome

If you are using /paymentMethods to show which payment methods are available to the shopper,
specify the following combination of countryCode and amount.currency:

Country/region countryCode amount.currency
Malaysia MY MYR
Singapore SG SGD

We provide an Atome logo which you can use on your payment form. For more information, refer to Downloading logos.

To perform risk checks, Atome requires you to collect the following shopper details:

  • Shopper's full name
  • Email address
  • Phone number
  • Billing address and delivery address

Make a payment

Make a /payments request from your server, specifying:

Parameter Required Description
paymentMethod -white_check_mark- Set to atome.
shopperName -white_check_mark- The shopper's full name.
shopperEmail -white_check_mark- The shopper's email address.
telephoneNumber -white_check_mark- The shopper's phone number.
billingAddress -white_check_mark- The postal address to be included on the invoice.
lineItems -white_check_mark- Price and product information about the purchased items.
returnUrl -white_check_mark- The URL where the shopper is redirected back to after completing the payment.
deliveryAddress The postal address where the goods will be shipped. Optional if billingAddress and deliveryAddress are the same.

The following example shows how to make a payment of SGD 10.

In the /payments response, note the action object. This contains the information needed to redirect the shopper.

Handle the redirect

  1. To complete the payment, redirect the shopper to the action.url returned in the /payments response, taking into account the following recommendations:

    • When using the HTTP GET method:
      For security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.

    • Redirection for mobile integrations:
      For mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.

  2. After the shopper is