API Overview

Payments Developer Guide
- Recent Revisions to This Document

Introduction to Payments
- Financial Institutions and Payment Networks
  - Merchant Financial Institutions (Acquirers)
  - Customer Financial Institutions (Issuers)
  - Payment Networks
  - Payment Processors
- Card Types
- Transaction Types
  - Card-Not-Present Transactions
- Payment Services
  - Sales
    - Sales with 3-D Secure
  - Credits
    - Credit Workflow
  - Voids
- Testing the Payment Services
  - Requirements for Testing
  - Test Card Numbers

Standard Payment Processing
- Account Verification Request
  - Required Fields for Processing an Account Verification Request
  - Simple Order Example: Processing a Zero Amount Authorization
- Sale
  - Required Fields for Processing a Sale
  - Additional Required Fields for Specific Sales Transactions
- Sale Bundled with Payer Authentication Enroll Service
- Sale Bundled with Payer Authentication Validate Service
- Follow-On Credits
  - Required Fields for Processing a Follow-On Credit
  - payments-processing-basic-refund-ex-rest-eftpos
  - Simple Order Example: Processing a Follow-On Credit
- Stand-Alone Stand-Alone Credits
  - Required Fields for Processing a Stand-Alone Credit
  - Simple Order Example: Processing a Stand-Alone Credit
- Void for a Sale or Stand-Alone Credit Transaction
  - Required Fields for Voiding a Sale
  - payments-processing-sale-standalone-credit-void-ex
- Stand-Alone CreditTimeout Void for a Sale or a Stand-Alone Credit Transaction
  - Required Fields for a Time-Out Void for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit
  - Simple Order Example: Time-Out Void for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit

On This Page

Required Fields for Voiding a Sale

merchantID
merchantReferenceCode
voidService_voidRequestID: Set this field to the request ID that was included in the sale response message.
voidService_run: Set the value to
true
.

clientReferenceInformation.code

Back to top