- Introduction to Payments
- Standard Payment Processing
- Debit and Prepaid Card Processing
- Payer Authentication Processing
- Processing Payments Using Credentials
- Customer-Initiated Transactions with Credentials on File
- Reauthorization Transaction
- Merchant-Initiated Reauthorization Transactions with PAN
- Installment Payments
- Recurring Payments
- Merchant-Initiated Recurring Payments with PAN
- Unscheduled COF Payments
- Token Management Service Processing
Required Fields for Authorizing a Customer-Initiated
Recurring Payments with Enrollable Network Tokens
Chase Paymentech SolutionsREST API
- paymentInformation.tokenizedCard.number
- Set the value to1.
- Set the value toTOKEN_CREATE.
- Set the value toinstrumentIdentifier.
- Set the value tointernet,MOTO, or a payer authentication value.
- processingInformation.paymentSolution
- Set to one of these possible values:
- 001: Apple Pay
- 004:CybersourceIn-App Solution
- 005: Masterpass
- 006: Android Pay
- 007: Chase Pay
- 008: Samsung Pay
- 012: Google Pay
- 014: Mastercard credential-on-file (COF) payment network token
- 015: Visa credential-on-file (COF) payment network token
- 027: Click to Pay
- visacheckout:Visa Click to Pay.
IMPORTANT
When relaxed requirements for address data and the expiration date are being used, not all fields
in this list are required. It is your responsibility to determine whether your
account is enabled to use this feature and which fields are required. For details
about relaxed requirements, see Relaxed Requirements for Address Data and Expiration Date in Payment Transactions.