Recent Revisions to This Document

About This Guide

Introduction to Payments
- Payment Services
- Financial Institutions and Payment Networks
  - Merchant Financial Institutions (Acquirers)
  - Issuing (Customer) Financial Institutions
  - Payment Networks
  - Payment Processors
- Card Types
  - Co-Badged Cards
  - Co-Branded Cards
  - Credit Cards
  - Debit Cards
  - Prepaid Cards
  - Private Label Cards
  - Quasi-Cash
- Transaction Types
  - Card-Not-Present Transactions
  - Card-Present Transactions
  - Authorizations with Card Verification Numbers
    - CVN Locations and Terminology
    - International Transactions
      - Dynamic Currency Conversion
      - Merchant Remittance Funding
- Payment Processing
  - Authorizations
    - Online Authorizations
    - Offline Authorizations
    - Incremental Authorizations
      - Example
    - Authorization Workflow
  - Sales
    - Dual Message Processing
      - Partial Authorizations
    - Single Message Processing
  - Authorization Reversals
  - Credits
    - Credit Workflow
  - Capture or Credit Voids
  - Capture
    - Capture Workflow

Payer Authentication Processing

Stored Credential Processing
- 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
    - credentials-mit-recur-intro
    - 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

Processing Token Management Service Payments
- Authorize a Payment with a Customer Token
  - tms-cust-tkn-pay-reqfields
- Authorize a Payment with a Non-Default Shipping Address
  - tms-ship-addr-make-pay-nondefault-ship-addr-reqfie
- Authorize a Payment with Non-Default Payment Instrument
  - tms-cust-pi-tkn-pay-nondefault-pi-reqfields
  - tms-cust-pi-tkn-pay-nondefault-pi-optfields
- Authorize a Payment with a Payment Instrument
  - tms-pi-tkn-pay-reqfields
  - tms-pi-tkn-pay-optfields
- Authorize a Payment with an Instrument Identifier
  - tms-ii-tkn-pay-reqfields
- Authorize a Payment with Legacy Token
  - tms-legacy-tkn-pay-reqfields
- Make a Credit with a Customer Token
  - tms-cust-tkn-credit-reqfields
- Make a Credit with Non-Default Payment Instrument
  - tms-cust-pi-tkn-credit-nondefault-pi-reqfields
  - tms-cust-pi-tkn-credit-nondefault-pi-optfields
- Make a Credit with a Payment Instrument
  - tms-pi-tkn-credit-reqfields
- Make a Credit with an Instrument Identifier
  - tms-ii-tkn-credit-reqfields
- Make a Credit with Legacy Token
  - tms-legacy-tkn-credit-reqfields

Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
  - Required Fields for Debit and Prepaid Authorizations Using Simple Order APIs
    - payments-debit-prepaid-auth-required-country
  - Optional Field for Debit and Prepaid Authorizations Using Simple Order APIs
  - SO Example: Debit and Prepaid Authorizations
- Enabling Debit and Prepaid Partial Authorizations
  - Required Field for Enabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Optional Field for Enabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Enabling Partial Authorizations
  - Example: Enabling Debit and Prepaid Partial Authorizations Using the Simple Order API
- Disabling Debit and Prepaid Partial Authorizations
  - Required Field for Disabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Optional Field for Disabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Disabling Partial Authorizations
  - Example: Disabling Debit and Prepaid Partial Authorizations Using the Simple Order API

On This Page

Simple Order API | null

Processing Debit and Prepaid Authorizations

This section provides the minimum set of information required to perform a successful authorization using debit and prepaid cards.

Endpoint

Set the

ccAuthService_run

field to

true

.

Send the request to

https://ics2ws.ic3.com/commerce/1.x/transactionProcessor

.

Back to top