Card on File
Authorize Card
POST
Save a customer’s card for future charges without taking a payment. Atoa returns a secure hosted page link — the customer enters their card details and completes 3DS verification, and the card is stored against their customer profile, ready to charge later.
Request Body Schema
All fields are optional — an empty body
Response
After the customer completes the hosted page flow, retrieve the saved card with List Payment Methods and use its
No amount is involved and no money moves. The customer sees a 3DS verification, not a payment. Money moves only when you call Charge Saved Card.
Card details are captured exclusively on Atoa’s PCI-compliant hosted page — they never touch your systems. Each call generates a fresh single-purpose link; request a new one rather than reusing old links.
Authorization
Bearer<accessSecret>
Path Parameters
string
required
The Atoa customer UUID returned by the Create Customer API. This is not your own merchant reference for the customer.
{} is valid.
boolean
default:"false"
When
true, Atoa delivers the link to the customer by email; if the customer has no email, by SMS. The link is also returned in the response either way. Fails with 400 if the customer has neither an email address nor a phone number.string
Where the hosted page redirects the customer after the card is saved successfully.
string
Where the hosted page redirects the customer if saving the card fails.
string
Secure hosted page URL. Open it in a browser, embed it in a WebView, or share it with the customer. Once they complete card entry and 3DS, the card is saved — there is no separate confirmation call to make.
id as paymentMethodId when charging.