- 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
Subsequent MIT Recurring Payments
After the initial CIT recurring payment, subsequent recurring payments are
merchant-initiated transactions (MITs).
Fields Specific to this Use Case
Include these fields with a standard authorization request when processing a
merchant-initiated subsequent recurring payment transaction:
- ccAuthService_commerceIndicator
- Set torecurringto indicate this is an installment transaction.
- subsequentAuth
- Set the field totrueto indicate this is a subsequent authorization.
- subsequentAuthStoredCredential
- Set the field totrueto indicate previously stored customer credentials were used.
- subsequentAuthTransactionID
- Include the previous transaction ID.
- subsequentAuthReason
- Set the reason code field to7.Only required for Mastercard transactions.
Endpoint
Set the
ccAuthService_run
field to true
.Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.