POST /tokens/create_using_temp_token

The device from which the customer has made the request

Default value: "application/x-www-form-urlencoded"

skip only webhooks

Valid values:

• "all-disabled"

If the site has multiple business entities, you can use this custom HTTP header to specify the business entity for which Chargebee should perform the operation.

skip all actions to be done on the events

Valid values:

• "all-disabled"

The email address of your customer/user. Use this when the email address has only ASCII characters.

The IP address of the customer where the request originated

The Base64-encoded email address of your customer/user. Use this if the email address has UTF-8 characters. When this header is provided, the header chargebee-request-origin-user is ignored.

skip only emails

Valid values:

• "all-disabled"

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.

Parameters for token_billing_address

Address line 2, as available in card billing address.

Address line 1, as available in card billing address.

The ISO 3166-2 state/province code without the country prefix. Currently supported for USA, Canada and India. For instance, for Arizona (USA), set state_code as AZ (not US-AZ). For Tamil Nadu (India), set as TN (not IN-TN). For British Columbia (Canada), set as BC (not CA-BC).

Postal or Zip code, as available in card billing address.

The state/province name.

The billing address country of the customer. Must be one of ISO 3166 alpha-2 country code.

Note: If you enter an invalid country code, the system will return an error.

City, as available in card billing address.

The gateway account to which the token is associated.

Type of payment method of the token. * google_pay - Payments made via Google Pay. * apple_pay - Payments made via Apple Pay. * unionpay - Payments made via UnionPay. * ideal - Payments made via iDEAL. * amazon_payments - Payments made via Amazon Payments. * bancontact - Payments made via Bancontact Card. * netbanking_emandates - Netbanking (eMandates) Payments. * alipay - Payments made via Alipay.
This payment source is deprecated. * card - Card based payment including credit cards and debit cards. Details about the card can be obtained from the card resource. * dotpay - Payments made via Dotpay. * giropay - Payments made via giropay. * upi - UPI Payments. * sofort - Payments made via Sofort. * direct_debit - Represents bank account for which the direct debit or ACH agreement/mandate is created. * generic - Payments made via Generic Payment Method. * wechat_pay - Payments made via WeChat Pay.
This payment source is deprecated. * paypal_express_checkout - Payments made via PayPal Express Checkout.

Valid values:

• "upi"
• "online_banking_poland"
• "unionpay"
• "direct_debit"
• "netbanking_emandates"
• "giropay"
• "venmo"
• "payconiq_by_bancontact"
• "card"
• "klarna_pay_now"
• "faster_payments"
• "sepa_instant_transfer"
• "alipay"
• "bancontact"
• "amazon_payments"
• "sofort"
• "automated_bank_transfer"
• "paypal_express_checkout"
• "apple_pay"
• "pay_to"
• "generic"
• "dotpay"
• "google_pay"
• "wechat_pay"
• "ideal"

• 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

Parameters for token_additional_detail

Cardholder's last name

Cardholder's first name

Card expiry year.

Card expiry month.

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.