Atome for API only

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

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:

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		Set to atome.
shopperName		The shopper's full name.
shopperEmail		The shopper's email address.
telephoneNumber		The shopper's phone number.
billingAddress		The postal address to be included on the invoice.
lineItems		Price and product information about the purchased items.
returnUrl		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 redirected back to your website, check the payment result by making a POST /payments/details request, specifying:

   • details: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.

3. In the response note the following:

   • resultCode: use this to present the result to your shopper.
   • pspReference: our unique identifier for the transaction.

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for Atome are:

If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment:

Refunds and cancellations

Partial refunds

To partially refund a payment, specify in your /payments/{paymentPspReference}/refunds request:

• amount: The amount to be refunded to the shopper.

Test and go live

To test Atome payments, you need a test shopper account in the Atome sandbox environment. To request a test account, reach out to your Adyen contact. If you are testing in multiple countries/regions, use a different test account for each location.

To test the QR code flow, download one of the following test apps:

For Malaysia (MY)

• Android app
• iOS app

For Singapore (SG)

• Android app
• iOS app

You can check the status of test payments in your Customer Area > Transactions > Payments.

To accept live Atome payments, you must contact our Support Team to add Atome in your live Customer Area.

See also