Stored Credential Processing
- Industry Practice Transactions
- Standing Instructions Transactions
  - Requirements for Standing Instruction Transactions
  - Recurring Billing for Recurring Payments

Transaction Matrix for Industry Practice and Standing Instructions
- Initial Transactions
- Subsequent Transactions

Customer-Initiated Transactions with Credentials on File
- Storing Customer Credentials with a Customer-Initiated Transaction
  - Required Fields
  - SO Example: Storing Customer Credentials During a Customer-Initiated Transaction
- Using Stored Customer Credentials During a Customer-Initiated Transaction
  - Required Fields
  - Card-Specific Required Fields
  - SO Example: Retrieving Customer Credentials During a Customer-Initiated Transaction

Merchant-Initiated Transactions
- Industry Practice Transactions
  - Merchant-Initiated Delayed Transaction
    - Required Fields
    - Card-Specific Required Fields
    - SO Example: Merchant-Initiated Delayed Authorization Transaction
  - Merchant-Initiated Incremental Transaction
    - Required Fields
    - Card-Specific Required Fields
    - SO Example: Merchant-Initiated Incremental Authorization
  - Merchant-Initiated Reauthorization Transactions
    - Required Fields
    - Card-Specific Required Fields
    - SO Example: Merchant-Initiated Reauthorization Transaction
  - Merchant-Initiated Resubmission Transaction
    - Required Fields
    - Card-Specific Required Fields
    - SO Example: Merchant-Initiated Resubmitted Authorization Transaction
  - Merchant-Initiated No-Show Transactions
    - Required Fields
    - Card-Specific Required Fields
    - SO Example: Merchant-Initiated No-Show Transaction
- Standing Instruction Transactions
  - Installment Payments
    - Initial CIT Installment Payment
      - Required Fields for Authorizing Initial Installment Payments Using Simple Order APIs
      - Card-Specific Required Fields
      - SO Example: Initial Customer-Initiated Transaction Installment Payment
    - Subsequent MIT Installment Payments
      - Required Fields for Authorizing Subsequent Installment Payments Using Simple Order APIs
      - Card-Specific Required Fields
      - SO Example: Subsequent Installment Authorization
  - Recurring Payments
  - Recurring Billing for Recurring Payments
  - Initial CIT Recurring Payment with a PAN
    - Required Fields for Authorizing Initial Recurring Payments Using Simple Order APIs
    - SO Example: Initial CIT Recurring Payment
  - Mastercard Standing Order Payments
    - Mastercard Initial CIT Standing Order Payment
      - Required Fields for Authorizing Standing Order Payments Using Simple Order APIs
      - SO Example: Initial CIT Standing Order Payment
  - Mastercard Subscription Payments
    - Mastercard Initial CIT Subscription Payment
      - Required Fields for Authorizing Subscription Payments Using Simple Order APIs
      - SO Example: Initial CIT Subscription Payment
  - Unscheduled COF Payments
    - Initial CIT Unscheduled COF Payment
      - Required Fields for Authorizing Initial Unscheduled COF Payments Using Simple Order APIs
      - SO Example: Initial CIT Unscheduled COF Payment

On This Page

Simple Order API | Visa Platform Connect

Merchant-Initiated Resubmission Transaction

A resubmission transaction is used when a merchant resubmits an authorization to recover an outstanding debt from the customer. A common scenario is when a card was initially declined due to insufficient funds, but the goods or services were already delivered to the customer.

Specific Fields for this Use Case

Include these fields with a standard authorization request:

subsequentAuth

–

Set the field to

true

to indicate this transaction is a merchant-initiated follow-on transaction.

subsequentAuthReason

–Set the reason field to

1

.