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
  - Simple Order Example: Storing Customer Credentials During a CIT
- 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
  - Simple Order 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
  - Simple Order Example: Processing a Merchant-Initiated Delayed Authorization Transaction

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
  - Simple Order Example: Processing a Merchant-Initiated Reauthorized Transaction

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
  - Simple Order Example: Processing a Merchant-Initiated Resubmitted Transaction

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
  - Simple Order Example: Processing Merchant-Initiated No-Show Transactions

Recurring Payments
- Customer-Initiated Recurring Payment with PAN
  - Required Fields for Authorizing a Customer-Initiated Recurring Payment with PAN Using Simple Order API
  - Simple Order Example: Authorizing a Customer-Initiated Recurring Payment with a PAN
- Merchant-Initiated Recurring Payments with PAN
  - Required Fields for Authorizing a Merchant-Initiated Recurring Payment
    - Card-Specific Required Fields for Authorizing Subsequent Recurring Payments
  - Simple Order Example: Authorizing a Merchant-Initiated Recurring Payment

Mastercard Standing Order Payments
- Mastercard Initial CIT Standing Order Payment
  - Required Fields for Authorizing Initial CIT Standing Order Payments
  - Simple Order Example: Authorizing Initial CIT Standing Order Payments

Mastercard Subscription Payments
- Mastercard CIT Initial Subscription Payment
  - Required Fields for Authorizing CIT Initial Subscription Payments
  - Simple Order 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
  - Simple Order Example: Authorizing Initial CIT Unscheduled COF Payments
- 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
  - Simple Order Example: Authorizing Subsequent MIT Unscheduled COF Payments

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

On This Page

Simple Order API | Elavon

Required Fields for Authorizing a Merchant-Initiated Recurring Payment

Use these required fields to authorize subsequent recurring payments.

Back to top