> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Atome via Adyen

> Set up Atome payments through Adyen in Payrails, and see the customer, address and order fields Atome requires.

export const SupportedWorkflowsTable = ({workflows, workflowKeys}) => {
  const hideUnsupportedWorkflows = ["interoperability"];
  if (!workflows) {
    return <p>
                <em>
                    No workflow data configured for this method yet — add it to
                    its file in <code>snippets/payment-methods/methods/</code>.
                </em>
            </p>;
  }
  return <table>
            <thead>
                <tr>
                    <th>Workflow</th>
                    <th>Supported</th>
                </tr>
            </thead>
            <tbody>
                {workflowKeys.filter(w => workflows[w.key] !== false || !hideUnsupportedWorkflows.includes(w.key.toLowerCase())).map(w => {
    const value = workflows[w.key];
    const display = value === true ? "✔" : value === false ? "✖" : value === "pending" ? "⏳" : value === null ? "N/A" : value;
    return <tr key={w.key}>
                                <td>
                                    {w.href ? <a href={w.href}>{w.label}</a> : w.label}
                                </td>
                                <td>{display}</td>
                            </tr>;
  })}
            </tbody>
        </table>;
};

export const method = {
  slug: "atome",
  name: "Atome",
  href: "/docs/orchestration/payment-methods/atome",
  workflows: {
    sdk: true,
    api: true,
    delayedCapture: false,
    instantCapture: true,
    cancelVoid: false,
    refund: true,
    saveInstruments: false,
    mit: false,
    interoperability: false
  },
  countries: [{
    code: "SG",
    name: "Singapore",
    continent: "Asia Pacific"
  }],
  providers: [{
    code: "adyen",
    name: "Adyen",
    href: "/docs/orchestration/payment-methods/atome/adyen",
    workflows: {
      sdk: true,
      api: true,
      delayedCapture: false,
      instantCapture: true,
      cancelVoid: false,
      refund: true,
      saveInstruments: false,
      mit: false,
      interoperability: false
    }
  }]
};

export const WORKFLOW_KEYS = [{
  key: "sdk",
  label: "Payrails SDK"
}, {
  key: "api",
  label: "Payrails API"
}, {
  key: "delayedCapture",
  label: "Delayed / Manual Capture",
  href: "/docs/orchestration/payment-acceptance/capture-and-cancel-modes#capture-mode"
}, {
  key: "instantCapture",
  label: "Instant Capture",
  href: "/docs/orchestration/payment-acceptance/capture-and-cancel-modes#capture-mode"
}, {
  key: "cancelVoid",
  label: "Cancel / Void",
  href: "/docs/orchestration/payment-acceptance/cancel-a-payment"
}, {
  key: "refund",
  label: "Refund / Reverse",
  href: "/docs/orchestration/payment-acceptance/refund-a-payment"
}, {
  key: "saveInstruments",
  label: "Save Instruments",
  href: "/docs/resources/manage-instruments"
}, {
  key: "mit",
  label: "Merchant Initiated Transaction (MIT)",
  href: "/docs/resources/payments/authorization-flags"
}, {
  key: "interoperability",
  label: "Interoperability"
}];

export const provider = method.providers.find(p => p.code === "adyen");

Accept [Atome](/docs/orchestration/payment-methods/atome) payments from customers in Singapore with Adyen as the payment service provider (PSP). The customer selects Atome, approves the payment plan in Atome, and returns to your site.

## Supported workflows

<SupportedWorkflowsTable workflows={provider.workflows} workflowKeys={WORKFLOW_KEYS} />

## Before you begin

Complete these steps before you send your first Atome payment through Adyen:

1. Set up an Adyen integration in your workspace. Follow the [Adyen integration setup guide](/docs/orchestration/integrations/adyen) if you don't have one yet.
2. Ask Adyen to enable Atome on your Adyen merchant account. For testing, ask Adyen for an Atome test shopper account.
3. Configure Adyen webhook notifications for your integration.
4. In the Payrails Portal, go to **Settings → Integrations**, open your Adyen integration, select **Atome** under **Payment methods**, and save.
5. Add Atome as a [payment option](/docs/orchestration/payment-methods/set-up-payment-methods) in your workflow.

## Request fields for Adyen

Send these fields in the authorize request, in addition to the standard [authorize fields](/reference/authorizeaction). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `amount.currency` | Required | Must be `SGD`. Payrails rejects other currencies. |
| `meta.customer.country.code` | Required | Must be `SG`. Sent to Adyen as the country code. |
| `meta.customer.email` | Required | Sent to Adyen as the shopper email. |
| `meta.customer.name`, `meta.customer.lastName` | Required | Sent to Adyen as the shopper name. Payrails needs both. |
| `meta.order.billingAddress` | Required | Needs `street`, `doorNumber`, `city`, `postalCode` and `country.code`. Sent to Adyen as the billing address. |
| `meta.order.billingAddress.phone` | Required | The customer's phone, with `countryCode` and `number`. Payrails also accepts `meta.order.deliveryAddress.phone`, and uses it first when you send both. Sent to Adyen as the telephone number, for example `6591234567`. |
| `meta.order.lines` | Required | At least one line item. Each line needs `id`, `name`, `quantity` and `unitPrice`. Sent to Adyen as line items. |
| `meta.order.deliveryAddress` | Optional | Sent to Adyen as the delivery address. |

## Authorize an Atome payment

Call [authorize a payment](/reference/authorizeaction) with `atome` as the `paymentMethodCode`. The response includes the redirect to Atome.

```json Authorize request theme={null}
{
  "amount": {
    "value": "120.00",
    "currency": "SGD"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "atome",
      "amount": {
        "value": "120.00",
        "currency": "SGD"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Wei",
      "lastName": "Tan",
      "email": "wei.tan@example.com",
      "country": {
        "code": "SG"
      }
    },
    "order": {
      "billingAddress": {
        "street": "Orchard Road",
        "doorNumber": "238",
        "city": "Singapore",
        "postalCode": "238851",
        "country": {
          "code": "SG"
        },
        "phone": {
          "countryCode": "65",
          "number": "91234567"
        }
      },
      "lines": [
        {
          "id": "item-1",
          "name": "Running shoes",
          "quantity": 1,
          "unitPrice": {
            "value": "120.00",
            "currency": "SGD"
          }
        }
      ]
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

After the customer approves the payment, Atome returns them to your `success` or `error` URL. Confirm the result through [webhook notifications](/docs/orchestration/payment-acceptance/receive-notifications) or the execution status before you fulfill the order.

## How Adyen handles Atome

* Payrails checks the customer, address and order fields before it calls Adyen, and names the missing field in the error.
* Payrails reads the phone number from the order's billing or delivery address, and sends it to Adyen with the dialing code and no `+`.
* Adyen captures Atome payments automatically. When Adyen confirms the authorization, Payrails also records the capture, so the payment completes in one step.
* Atome through Adyen supports customer-initiated payments only. Payrails rejects an MIT before it calls Adyen.


## Related topics

- [Atome](/docs/orchestration/payment-methods/atome.md)
- [FPX via Adyen](/docs/orchestration/payment-methods/fpx/adyen.md)
- [Przelewy24 via Adyen](/docs/orchestration/payment-methods/przelewy24/adyen.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.