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
  - REST Example: Storing Customer Credentials During a Customer-Initiated Transaction
- Using Stored Customer Credentials During a Customer-Initiated Transaction
  - Required Fields
  - Card-Specific Required Fields
  - REST 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
    - REST Example: Merchant-Initiated Delayed Authorization Transaction
  - Merchant-Initiated Incremental Transaction
    - Required Fields
    - Card-Specific Required Fields
    - REST Example: Merchant-Initiated Incremental Transaction
  - Merchant-Initiated Reauthorization Transactions
    - Required Fields
    - Card-Specific Required Fields
    - REST Example: Merchant-Initiated Reauthorization Transactions
  - Merchant-Initiated Resubmission Transaction
    - Required Fields
    - Card-Specific Required Fields
    - REST Example: Merchant-Initiated Resubmitted Authorization Transactions
  - Merchant-Initiated No-Show Transactions
    - Required Fields
    - Card-Specific Required Fields
    - REST Example: Merchant-Initiated No-Show Transaction
- Standing Instruction Transactions
  - Installment Payments
    - Initial CIT Installment Payment
      - Required Fields for Authorizing Initial Installment Payments Using REST APIs
      - Card-Specific Required Fields
      - REST Example: Initial Customer-Initiated Transaction Installment Payment
    - Subsequent MIT Installment Payments
      - Required Fields for Authorizing Subsequent Installment Payments Using REST APIs
      - Card-Specific Required Fields
      - REST Example: Subsequent Installment Payment Authorization
  - Recurring Payments
    - Recurring Billing for Recurring Payments
    - Initial CIT Recurring Payment
      - Required Fields for Authorizing Initial Recurring Payments Using REST APIs
      - REST Example: Initial CIT Recurring Payment
  - Mastercard Standing Order Payments
    - Mastercard Initial CIT Standing Order Payment
      - Required Fields for Authorizing Standing Order Payments Using REST APIs
      - REST Example: Initial CIT Standing Order Payments
  - Mastercard Subscription Payments
    - Mastercard Initial CIT Subscription Payment
      - Required Fields for Authorizing Subscription Payments Using REST APIs
      - REST Example: Initial CIT Subscription Payments
  - Unscheduled COF Payments
    - Initial CIT Unscheduled COF Payment
      - Required Fields for Authorizing Initial Unscheduled COF Payments Using REST APIs
      - REST Example: Initial CIT Unscheduled COF Payment

On This Page

REST API | Visa Platform Connect

Merchant-Initiated No-Show Transactions

A no-show authorization occurs when a merchant charges a customer after the customer makes a reservation, and does not show up to claim the reservation. In this situation, the customer is charged an agreed upon fee for not showing up as expected.

Fields Specific to this Use Case

Include these fields with a standard authorization request:

processingInformation.authorizationOptions.initiator.type

–

Set the field to

merchant

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

processingInformation.authorizationOptions.initiator.merchantInitiatedTransaction.reason

–Set the reason field to

4

.