API Overview

Credentialed Transactions
- Recent Revisions to This Document

Introduction to Credentialed Transactions
- Industry Practice Transactions
- Standing Instructions Transactions
  - Requirements for Standing Instruction Transactions
  - Recurring Billing for Recurring Payments
- Transaction Matrix for Industry Practice and Standing Instructions

Customer-Initiated Transactions with Credentials on File
- Storing Customer Credentials with a CIT and PAN
  - Required Fields for Storing Customer Credentials During a CIT
  - REST Example: Storing Customer Credentials During a CIT
- Storing Customer Credentials with a CIT and TMS
  - Required Fields for Storing a Customers Credentials with a CIT and TMS
  - Example: Storing a Customer's Credentials with a CIT and TMS
- Using Stored Customer Credentials During a CIT
  - Required Fields for Retrieving Customer Credentials During a Customer-Initiated Transaction
    - Card-Specific Required Field for Retrieving Customer Credentials During a CIT
  - REST Example: Retrieving Customer Credentials During a CIT

Delayed Transaction
- Merchant-Initiated Delayed Transaction with PAN
  - Required Fields for Processing a Merchant-Initiated Delayed Transaction
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
  - REST Example: Processing a Merchant-Initiated Delayed Authorization Transaction
- Merchant-Initiated Delayed Transaction with TMS
  - Required Fields for MIT Delayed Transaction with TMS
  - Example: MIT Delayed Transaction with TMS Instrument Identifier
  - Example: MIT Delayed Transaction with TMS Payment Instrument
  - Example: MIT Delayed Transaction with TMS Customer token

Incremental Transaction
- Merchant-Initiated Incremental Transaction with PAN
  - Required Fields for Processing Merchant-Initiated Incremental Transactions
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
  - REST Example: Processing Merchant-Initiated Incremental Transactions
- Merchant-Initiated Incremental Transaction with TMS
  - Required Fields for MIT Incremental Transaction with TMS
  - Example: MIT Incremental Transaction with a TMS Instrument Identifier
  - Example: MIT Incremental Transaction with a TMS Payment Instrument
  - Example: MIT Incremental Transaction with a TMS Customer token

Reauthorization Transaction
- Merchant-Initiated Reauthorization Transactions with PAN
  - Required Fields for Processing Merchant-Initiated Reauthorized Transactions
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
  - REST Example: Processing a Merchant-Initiated Reauthorized Transaction
- Merchant-Initiated Reauthorization Transactions with TMS
  - Required Fields for MIT Reauthorization Transaction with TMS
  - Example: MIT Reauthorization Transaction with a TMS Instrument Identifier
  - Example: MIT Reauthorization Transaction with a TMS Payment Instrument
  - Example: MIT Reauthorization Transaction with a TMS Customer

Resubmission Transaction
- Merchant-Initiated Resubmission Transaction with PAN
  - Required Fields for Processing a Merchant-Initiated Resubmitted Transaction
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
  - REST Example: Processing a Merchant-Initiated Resubmitted Transaction
- Merchant-Initiated Resubmission Transaction with TMS
  - Required Fields for MIT Resubmission Transaction with TMS
  - Example: MIT Resubmission Transaction with a TMSInstrument Identifier
  - Example: MIT Resubmission Transaction with a TMSPayment Instrument
  - Example: MIT Reauthorization Transaction with a TMS Customer

No-Show Transactions
- Merchant-Initiated No-Show Transactions with PAN
  - Required Fields for Processing Merchant-Initiated No-Show Charges
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
  - Optional Field for Processing Merchant-Initiated No-Show Charges
  - REST Example: Processing Merchant-Initiated No-Show Transactions
- Merchant-Initiated No-Show Transaction with TMS
  - Required Fields for MIT No-Show Transaction with TMS
  - Example: MIT No-Show Transaction with a TMS Instrument Identifier
  - Example: MIT No-Show Transaction with a TMS Payment Instrument
  - Example: MIT No-Show Transaction with a TMS Customer

Recurring Payments
- Customer-Initiated Recurring Payment with PAN
  - Required Fields for Authorizing a Customer-Initiated Recurring Payment with PAN Using REST API
  - REST Example: Authorizing a Customer-Initiated Recurring Payment with a PAN
- Customer-Initiated Recurring Payment with TMS
  - Required Fields for Authorizing a Customer-Initiated Recurring Payment with TMS
  - REST Example: Authorizing a Customer-Initiated Recurring Payment with TMS
- Customer-Initiated Recurring Payment with Enrollable Network Tokens
  - Required Fields for Authorizing a Customer-Initiated Recurring Payments with Enrollable Network Tokens
  - REST Example: Authorizing a Customer-Initiated Recurring Payment with Enrollable Network Tokens
- Merchant-Initiated Recurring Payments with PAN
  - Required Fields for Authorizing a Merchant-Initiated Recurring Payment
    - Card-Specific Required Fields for Authorizing Subsequent Recurring Payments
  - REST Example: Authorizing a Merchant-Initiated Recurring Payment
- Merchant-Initiated Recurring Payments with TMS
  - Required Fields for Authorizing a Merchant-Initiated Recurring Payments with TMS
  - REST Example: Authorizing a Merchant-Initiated Recurring Payment with a TMS Instrument Identifier
  - REST Example: Authorizing a Merchant-Initiated Recurring Payment with TMS Payment Instrument
  - REST Example: Authorizing a Merchant-Initiated Recurring Payment with a TMS Customer Token

Mastercard Standing Order Payments
- Mastercard Initial CIT Standing Order Payment
  - Required Fields for Authorizing Initial CIT Standing Order Payments
  - REST Example: Authorizing Initial CIT Standing Order Payments
- Mastercard Initial CIT Standing Order Payment with TMS
  - Required Fields for Authorizing Initial CIT Standing Order Payments with TMS
  - REST Example: Authorizing Initial CIT Standing Order Payments with TMS

Mastercard Subscription Payments
- Mastercard CIT Initial Subscription Payment
  - Required Fields for Authorizing CIT Initial Subscription Payments
  - REST Example: Authorizing Initial CIT Subscription Payments
- Mastercard CIT Initial Subscription Payment with TMS
  - Required Fields for Authorizing CIT Initial Subscription Payments with TMS
  - REST Example: Authorizing Initial CIT Subscription Payments

Unscheduled COF Payments
- Customer-Initiated Unscheduled COF Payment with PAN
  - Required Fields for Authorizing Initial CIT Unscheduled COF Payments
  - REST Example: Authorizing Initial CIT Unscheduled COF Payments
- Customer-Initiated Unscheduled COF Payments with TMS
  - Required Fields for CIT Unscheduled COF Payments with TMS
  - REST Example: Initial CIT Unscheduled COF Payment in TMS
- Customer-Initiated Unscheduled COF Payment with Enrollable Network Tokens
  - Required Fields for CIT Unscheduled COF Payment with Enrollable Network Tokens
  - REST API Example: CIT Unscheduled COF Payment with Enrollable Network Tokens
- Merchant-Initiated Unscheduled COF Payments with PAN
  - Required Fields for Authorizing Subsequent MIT Unscheduled COF Payments
    - Card-Specific Required Field for Processing a Merchant-Initiated Transactions
  - REST Example: Authorizing Subsequent MIT Unscheduled COF Payments
- Merchant-Initiated Unscheduled COF Payments with TMS
  - Required Fields for MIT Unscheduled COF Payments with TMS
  - Example: MIT Unscheduled COF Payment with TMS Instrument Identifier
  - Example: MIT Unscheduled COF Payment with TMS Payment Instrument
  - Example: MIT Unscheduled COF Payment with TMS Customer

Reference Information
- Relaxed Requirements for Address Data and Expiration Date in Payment Transactions
  - Requirements
  - Services
  - Relaxed Fields

On This Page

Relaxed Requirements for Address Data and Expiration Date in Payment Transactions

With relaxed requirements for address data and the expiration date, not all standard payment request fields are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required.

Back to top