API Overview

eCheck Merchant Guide
- Recent Revisions to This Document

Introduction to the eCheck Service
- Requirements for Using the eCheck Service
- eCheck Transaction Types

Getting Started with the eCheck Service
- eCheck Application
  - Submitting the eCheck Application
  - Completing eCheck Application Fields
- Boarding Your Merchant Account for Sandbox Testing

Overview of eCheck Transaction Processing
- eCheck Settlement
  - eCheck Returns
  - eCheck Chargebacks
  - eCheck Credits and Refunds
- eCheck Transaction Statuses During Processing
- eCheck Integrations
- eCheck Risk Reserve
- eCheck Processing Limits and Settings
- eCheck Notice of Change
- Payment Authorization and Authentication for eCheck Transactions
- eCheck Records Retention Requirements

Manage eCheck Settings in the Business Center
- Managing Merchant Permissions in the Business Center
  - Creating Roles
  - Creating a User Account and Adding Roles
- Accessing eCheck Settings in the Business Center
  - eCheck Statements
    - eCheck Settlement Account Statements
    - eCheck Reserve Account Statements

Process eCheck Transactions Using the Business Center
- Submitting Transactions Using the Virtual Terminal
  - Configuring the Virtual Terminal to Process eCheck Transactions
  - Processing eCheck Transactions Using the Virtual Terminal
- Submitting Transactions Using Recurring Billing and Token Management Service
  - Creating an eCheck Recurring Subscription
  - Requesting an On-Demand Transaction
- eCheck Transaction Search and Details

Process eCheck Transactions Using the REST API
- Processing an eCheck Debit Transaction Using the REST API
  - Required Fields for an eCheck Debit Transaction
  - Optional Fields for an eCheck Debit Transaction
  - REST Example: eCheck Debit Transaction
- Processing a Recurring eCheck Debit Transaction Using the REST API
  - Required Fields for a Recurring eCheck Debit Transaction
  - REST Example: Recurring eCheck Debit Transaction
- Creating an eCheck Token Using the REST API
  - Required Fields for Creating an eCheck Token
  - REST Example: Creating an eCheck Token
- Creating an eCheck Token and Processing an eCheck Transaction Using the REST API
  - Required Fields for Creating an eCheck Token and Processing an eCheck Transaction
  - Optional Fields for Creating an eCheck Token and Processing an eCheck Transaction
  - REST Example: Creating an eCheck Token and Processing an eCheck Transaction
- Using an eCheck Token to Submit an eCheck Debit Transaction Using the REST API
  - Required Fields for Using an eCheck Token to Submit an eCheck Debit Transaction
  - Optional Fields for Using an eCheck Token to Submit an eCheck Debit Transaction
  - REST Example: Using an eCheck Token to Submit an eCheck Debit Transaction

Accepting eCheck Payments through Unified Checkout, Pay by Link, and Invoicing
- Accepting eCheck Payments through Unified Checkout
- Accepting eCheck Payments through Invoices
- Accepting eCheck Payments through Payment Links

eCheck Reconciliation Reports
- Funding Details Report
  - Fields in the Funding Details Report
- Chargeback Details Report
  - Fields in the Chargeback Details Report
- Deposit Details Report
  - Deposit Details Report Line Items
  - Fields in the Deposit Details Report

eCheck Reconciliation Reporting Case Study
- Day 1
- Day 2
- Day 3
- Day 4
- Day 5
- Day 6
- Day 7
- Day 8

On This Page

Creating an eCheck Token and Processing an eCheck Transaction Using the REST API

This section shows how to create an eCheck transaction along with an eCheck transaction using the REST API.

IMPORTANT

The token can also be used for future eCheck transactions for this customer.

Creating an eCheck Token and Processing an eCheck Transaction

Follow these steps to create an eCheck token for your customer and process an eCheck transaction at the same time:

Create the message with the required API fields.

Send the message to one of these endpoints:

Production:

POST https://api.cybersource.com/pts/v2/payments

Test:

POST https://apitest.cybersource.com/pts/v2/payments

Verify the response messages to make sure that the request was successful. A 200-level HTTP response code indicates success.

See Transaction Response Codes.

Back to top