Create using vault temp token

The gateway account to which the token is associated.

Type of payment method of the token.

Single-use token created by payment gateways. In Stripe, a single-use token is created for Apple Pay Wallet, card details or direct debit. In Braintree, a nonce is created for Apple Pay Wallet, PayPal, or card details. In Authorize.net, a nonce is created for card details. In Adyen, an encrypted data is created from the card details.

Represents what type of object at gateway eg. "token" in case Stripe token and "source" in case of Stripe Source.

Used to derieve Bank Account Scheme by default will take site default currency.

• checkout_com: While adding a new payment method using permanent token or passing raw card details to Checkout.com, document ID and country_of_residence are required to support payments through dLocal.

  • payer: User related information.
    • country_of_residence: This is required since the billing country associated with the user's payment method may not be the same as their country of residence. Hence the user's country of residence needs to be specified. The country code should be a two-character ISO code.
    • document: Document ID is the user's identification number based on their country.

• bluesnap: While passing raw card details to BlueSnap, if fraud_session_id is added, additional validation is performed to avoid fraudulent transactions.

  • fraud: Fraud identification related information.
    • fraud_session_id: Your BlueSnap fraud session ID required to perform anti-fraud validation.

• braintree: While passing raw card details to Braintree, your fraud_merchant_id and the user's device_session_id can be added to perform additional validation and avoid fraudulent transactions.

  • fraud: Fraud identification related information.
    • device_session_id: Session ID associated with the user's device.
    • fraud_merchant_id: Your merchant ID for fraud detection.

• chargebee_payments: While passing raw card details to Chargebee Payments, if fraud_session_id is added, additional validation is performed to avoid fraudulent transactions.

  • fraud: Fraud identification related information.
    • fraud_session_id: Your Chargebee Payments fraud session ID required to perform anti-fraud validation.

• bank_of_america: While passing raw card details to Bank of America, your user's device_session_id can be added to perform additional validation and avoid fraudulent transactions.

  • fraud: Fraud identification related information.
    • device_session_id: Session ID associated with the user's device.

• ecentric: This parameter is used to verify and process payment method details in Ecentric. If the merchant_id parameter is included, Chargebee will vault it / perform a lookup and verification against this merchant_id, overriding the one configured in Chargebee. If tokens and processing occur in the same Merchant GUID, you can just skip this part.

  • merchant_id: Merchant GUID where the card is vaulted or need to be vaulted.

• ebanx: While passing raw card details to EBANX, the user's document is required for some countries and device_session_id can be added to perform additional validation and avoid fraudulent transactions.

  • payer: User related information.
    • document: Document is the user's identification number based on their country.
  • fraud: Fraud identification related information.
    • device_session_id: Session ID associated with the user's device .