Skip to main content
Delivered when a customer saves a payment method for future payments, or removes a saved one. Use it to keep your own record of a customer’s saved payment methods in step with Atoa. type tells you the kind of payment method, and which detail object the payload carries. CARD carries cardDetails. metadata is the key/value data you attached when saving the card (see Authorize Card), and createdAt is when the card was saved. Both match what the List Payment Methods API returns, and are omitted when the card carried no metadata.
The detail object and its fields are optional — a field is omitted when the provider did not report it. Only status, type, customerId, paymentMethodId and businessId are guaranteed.
Use paymentMethodId to charge the saved payment method — see Charge Saved Card. Authorize Card generates the link a customer uses to save one.