paymentMethodToken
that enables:
paymentMethodToken
is paired with a customerId
which uniquely identifies identify a customer. You can use any unique identifier for this such as a UUID or an email address.
This customerId
is required for:
vaultOnSuccess
to save the customer’s payment data once it has been successfully authorizedPrimer's Vault
paymentMethod.vaultOnSuccess
flag in the Client Session API or the Payments API. When this flag is set to true, and if the payment method supports it, the payment method credentials are automatically added to the vault once the payment is successfully authorized.
Make sure to also pass customerId
to specify the customer’s vault this payment method should be added to.
Vaulting Token Flow
customerId
has been provided in the client session and the customer has vaulted payment methods stored with Primer. This enables your customers to seamlessly pay with one of their saved payment method.
We recommend to set paymentMethod.paymentType
to ECOMMERCE
in the client session or payment request. This ensures the right data is sent to the processor to maximize the authorization rate.
Universal Checkout Vault
captureVaultedCardCvv
option within the PAYMENT_CARD
payment method options in the POST /client-session
request. When set to true
, this flag activates the CVV recapture functionality in the Drop-In implementation, providing an out-of-the-box solution for transactions with vaulted payment cards.
Example Request:
customerId
. Each entry in the list contains a token
representing the payment method token to use to create a payment.
Parameter Name | Description |
---|---|
paymentMethodToken | The vaulted payment method token |
paymentMethod ↳ paymentType | Type of payment. Used to improve conversion.
|
Universal Checkout Vault