- Introduction to Payments
- Standard Payments Processing
- Card Present Connect | Retail Processing
- Card Present Connect | Mass Transit Processing
- Mass Transit Authorizations for a Tap-Initiated Debt Recovery with EMV Data
- Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
- Airline Data Processing
- Japanese Payment Options Processing
- Processing Payments Using Credentials
- Customer-Initiated Transactions with Credentials on File
- Merchant-Initiated Delayed Transaction
- Merchant-Initiated Incremental Transaction
- Merchant-Initiated No-Show Transactions
- Merchant-Initiated Reauthorization Transactions
- Merchant-Initiated Resubmission Transaction
- Installment Payments
- Recurring Payments
On This Page
Simple Order API | Visa Platform Connect
Initial CIT Recurring Payment with a PAN
The first transaction in a recurring payment is a customer-initiated transaction (CIT).
Before you can perform a subsequent merchant-initiated transaction (MIT), you must store
the customer's credentials for later use. Before you can store the user's credentials,
you must get the customer's consent to store their private information. This is also
known as establishing a relationship with the customer.
Fields Specific to this Use Case
Include these fields with a standard authorization request when storing customer
credentials during the initial CIT recurring payment:
- subsequentAuthFirst
- Set the field totrueto indicate the customer credentials will be stored for future use.
- subsequentAuth
- Set the field tofalseto indicate this transaction is a customer-initiated initial transaction.
- e_commerce_indicator
- Set the field tointernetor a payer authentication value.
In the CIT authorization response, save the Transaction ID. You must include the
network transaction ID in subsequent MIT recurring authorization requests.
Endpoint
Set the
ccAuthService_run
field to true
.Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.