API Overview

SEPA Direct Debit with Sentenial Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Direct Debits
- Mandate Requirements
- Direct Debit Batching Schedule
- Chargebacks
- Execution Date and Refund Period

Overview of Processing Direct Debits
- Create a Mandate Workflow
- Update a Mandate Workflow
- Revoke a Mandate Workflow
- Import a Mandate Workflow
- Process a Sale Workflow
- Cancel a Direct Debit Workflow
- Reverse a Direct Debit Workflow
- Refund a Direct Debit Workflow
- Create a Mandate Statuses Workflow
- Import a Mandate Statuses Workflow
- Process a Sale Statuses Workflow

Requesting Direct Debits
- Create a Mandate
  - Create a Mandate on the Fly
  - Required Fields for Creating a Mandate
  - Optional Fields for Creating a Mandate
  - Simple Order Example: Creating a Mandate
- Update a Mandate
  - Required Fields for Updating a Mandate
  - Optional Fields for Updating a Mandate
  - Test Triggers for Updating a Mandate
  - Simple Order Example: Updating a Mandate
- Import a Mandate
  - Required Fields for Importing a Mandate
  - Optional Fields for Importing a Mandate
  - Test Trigger for Importing a Mandate
  - Simple Order Example: Importing a Mandate Service
- Revoke a Mandate
  - Required Fields for Revoking a Mandate
  - Optional Field for Revoking a Mandate
  - Test Triggers for Revoking a Mandate
  - Simple Order Example: Revoking a Mandate
- Check a Mandate Status
  - Required Fields for Checking a Mandate Status
  - Simple Order Example: Checking Mandate Status
- Process a Direct Debit Sale
  - Required Fields for Processing a Direct Debit
  - Optional Fields for Processing a Direct Debit
  - Test Triggers for Processing Direct Debits
  - Simple Order Example: Processing a Direct Debit
- Check a Direct Debit Status
  - Required Fields for Checking Direct Debit Status
  - Test Triggers for Checking Statuses
  - Simple Order Example: Checking Direct Debit Status
- Cancel a Direct Debit
  - Required Fields for Cancelling a Direct Debit
  - Test Triggers for Cancelling a Direct Debit
  - Simple Order Example: Cancelling a Direct Debit
- Reverse a Direct Debit
  - Required Fields for Reversing a Direct Debit
  - Optional Field for Reversing a Direct Debit
  - Simple Order Example: Reversing a Direct Debit
- Refund a Direct Debit
  - Required Fields for Refunding a Direct Debit
  - Test Triggers for Refunds
  - Simple Order Example: Refunding a Direct Debit

Reference Information
- Merchant Account Types
- Reason Codes for SEPA Direct Debits for the Simple Order API
- Export Compliance Reason Codes
- Generating Reports Using the Business Center
- Terminology

Reverse a Direct Debit

You can reverse a direct debit before it is processed by the customer’s bank. The direct debit must be in the

settle_initiated

or

settle_accepted

status. To reverse a

pending

direct debit, send a cancel direct debit request instead. See Cancel a Direct Debit.

To reverse a direct debit after more than five days, or when the status is

settled

, send a refund request instead. See Refund a Direct Debit.

Endpoints

Set the

apCancelService_run

field to

true

, and send the request to one of these endpoints:

Production:

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

Test:

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

Response Statuses

The reversal service responds with one of these statuses in the

apCancelReply_status

field:

Accepted

: The cancellation request is being processed and Cybersource is trying to reverse the debit request with the inter-bank system.

Failed

: The original direct debit request is rejected by the customer's bank. A reversal is not necessary.

Reversed

: The direct debit was canceled during the

settle_accepted

status.

The reversal service also responds with a reason code in the

apCancelReply_reasonCode

field. For more information about reason codes, see the Reason Codes for SEPA Direct Debits for the Simple Order API.