GettingStarted
- CyberSource’s Payment Process

What Is REST?

REST Components

Registration

Authentication
- Create a Shared Secret Key for HTTP Signature Authentication
- Create a P12 Certificate for JSON Web Token Authentication

Generate the Header
- HTTP Signature Authentication
- JSON Web Token Authentication

Authorizations

Online Authorizations
- Payment Network Tokenization
- Apple Pay
- Android Pay
- Google Pay
- Samsung Pay
- Visa Click to Pay

Card-Present and EMV Authorizations

Captures
- Creating a Capture Request

Sales
- Creating a Sale Request

Voids
- Creating a Void Request

Refunds
- Creating a Refund Request

Credits
- Creating a Credit Request

Reversals

Electronic Check Services
- Electronic Check Processing
- Optional Features
- Testing Electronic Check Transactions
- NOC Codes
- Verification Codes
- SEC Codes

Service Fees
- Service Fees for Credit Card Transactions
- Service Fees in Electronic Check Transactions

Merchant-Initiated Transactions
- Descriptions
- Use Cases
  - Delayed Charge
  - Installment Payment
  - No-Show Transaction
  - Reauthorization
  - Recurring Payment
  - Resubmission
  - Unscheduled COF Transaction
- Merchant-Initiated Reversals and Voids
- Terminology

CVN

AVS Codes

Level II and Level III Payments
- Relaxed Requirements for Address Data and Expiration Date
- Decimals and Strings
- Numbered Elements
- Level II Data Captures and Credits
- Level III Data Captures and Credits

Response Codes

Online Authorizations

To create an authorization request using the a payment API,

POST

the payment card information to the REST API authorization resource Process a Payment.

You can use payment network tokenization to avoid sending sensitive payment card information or primary account numbers (PANs) in the authorization request.

On This Page

Top