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
    - 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
    - credentials-mit-recur-intro
    - Recurring Billing for Recurring Payments
    - Initial CIT Recurring Payment with a PAN
      - 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

Processing Token Management Service Payments
- Authorize a Payment with a Customer Token
  - Required Fields for Authorizing a Payment with a Customer Token Using the REST API
  - REST Example: Authorizing a Payment with a Customer Token
  - REST Example: Authorizing a Payment Using a Customer Token Linked to a Network Token
- Authorize a Payment with a Non-Default Shipping Address
  - Required Fields for Authorizing a Payment with a Non-Default Shipping Address Using the REST API
  - REST Example: Authorizing a Payment with a Non-Default Shipping Address
- Authorize a Payment with Non-Default Payment Instrument
  - Required Fields for Authorizing a Payment with Non-Default Payment Instrument Using the REST API
  - Optional Fields for Authorizing a Payment with Non-Default Payment Instrument Using the REST API
  - REST Example: Authorizing a Payment with Non-Default Payment Instrument
- Authorize a Payment with a Payment Instrument
  - Required Fields for Authorizing a Payment with a Payment Instrument Using the REST API
  - Optional Fields for Authorizing a Payment with a Payment Instrument Using the REST API
  - REST Example: Authorizing a Payment with a Payment Instrument
- Authorize a Payment with an Instrument Identifier
  - Required Fields for Authorizing a Payment with an Instrument Identifier Using the REST API
  - REST Example: Authorizing a Payment with an Instrument Identifier
  - REST Interactive Example: Authorizing a Payment with an Instrument Identifier
- Authorize a Payment with Legacy Token
  - Required Fields for Authorizing a Payment with Legacy Token Using the REST API
  - REST Example: Authorizing a Payment with Legacy Token
  - REST Interactive Example: Authorizing a Payment with a Legacy Token
- Make a Credit with a Customer Token
  - Required Fields for Making a Credit with a Customer Token Using the REST API
  - REST Example: Making a Credit with a Customer Token
- Make a Credit with Non-Default Payment Instrument
  - Required Fields for Making a Credit with Non-Default Payment Instrument Using the REST API
  - Optional Fields for Making a Credit with Non-Default Payment Instrument Using the REST API
  - REST Example: Making a Credit with Non-Default Payment Instrument
- Make a Credit with a Payment Instrument
  - Required Fields for Making a Credit with a Payment Instrument Using the REST API
  - REST Example: Making a Credit with a Payment Instrument
- Make a Credit with an Instrument Identifier
  - Required Fields for Making a Credit with an Instrument Identifier Using the REST API
  - REST Example: Making a Credit with an Instrument Identifier
  - REST Interactive Example: Making a Credit with an Instrument Identifier
- Make a Credit with Legacy Token
  - Required Fields for Making a Credit with Legacy Token Using the REST API
  - REST Example: Making a Credit with Legacy Token

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

On This Page

REST API | null

Merchant Remittance Funding

You can request that the transaction proceeds be converted to another currency. Currency conversion uses a foreign exchange rate to calculate the conversion to the requested currency. The foreign exchange rate might be explicitly stated as a rate or implicitly stated as a transaction amount. The funded amount and can vary from day to day. The foreign exchange rate might also include a mark-up for the foreign exchange risk, sales commissions, and handling costs.

Back to top