Introduction to Online Bank Transfers

On This Page
Online Bank Transfer services enables customers to pay for goods and services using online bank transfers from their bank accounts directly to your account.

Supported Payment Methods

Online Bank Transfers enables you to process transactions using these payment services:
  • Bancontact: e-commerce payment system in Belgium. It enables customers to pay for goods using direct bank transfers from their bank accounts directly to your account.
  • iDEAL: e-commerce payment system in the Netherlands. It enables customers to pay for goods using online bank transfers from their bank accounts directly to your account.

Bancontact

Bancontact is an e-commerce payment system in Belgium. It enables customers to pay for goods using direct bank transfers from their bank accounts directly to your account.
These banks support the Bancontact payment method:
  • ABK Bank
  • Argenta
  • Axa
  • Bank VanBreda
  • CPH Banque
  • Belfius
  • Beobank
  • BNP Paribas Fortis
  • Bpost Bank
  • CBC
  • Crelan
  • Deutsche Bank
  • ING
  • KBC
  • Keytrade Bank
  • Nagelmackers
  • Record Bank
  • VDK Spaarbank

iDEAL

iDEAL is an e-commerce payment system in the Netherlands. It enables customers to pay for goods using online bank transfers from their bank accounts directly to your account.
Following is a list of banks that support the iDEAL payment method and their option IDs.
  • ABN AMRO: ABNCNL2A
  • ASN Bank: ASNBNL21
  • Bunq: BUNQNL2A
  • Handelsbanken: HANDNL2A
  • ING Bank: INGBNL2A
  • Knab: KNABNL2H
  • Moneyou: MOYONLI21
  • Rabobank: RABONL2URSA
  • RegioBank: RBRBNL21
  • SNS Bank: SNSBNL2A
  • Triodos Bank: TRIONL2U
  • Van Lanschot: FVLBNL22
Cybersource
 recommends that you make the iDEAL payment method available to Belgian customers. A large number of Dutch nationals or Dutch bank account holders resides in Belgium, and they prefer to use their Dutch accounts.

Payment Method Workflows

This section describes the workflows for the different Online Bank Transfer payment methods.

Bancontact Workflow

This workflow describes the sequence of events that comprise a successful Bancontact transaction.
  1. The customer begins to checkout using Bancontact as a payment method and selects their bank.
  2. The merchant sends a sale API request to
    Cybersource
    . For more information, see Processing a Sale.
  3. Cybersource
     sends a
    pending
     status and a redirect URL to the merchant.
  4. The merchant redirects the customer to their issuing bank's website.
  5. The customer enters their Bancontact card information and is redirected to the merchant's success URL.
  6. The merchant displays payment confirmation to the customer.
  7. To confirm the updated payment status, the merchant sends a check status API request to
    Cybersource
     and includes the sale request ID. For more information, see Check Transaction Status.
  8. Cybersource
     sends a
    settled
     status to the merchant.

Bancontact Refund Workflow

This workflow describes the sequence of events that comprise a successful Bancontact refund.
  1. The customer initiates a refund to the merchant.
  2. The merchant sends a refund API request to
    Cybersource
     and includes the sale request ID. For more information, see Refund a Payment.
  3. Cybersource
     sends either a
    pending
     or
    refunded
     status to the merchant.
  4. The merchant displays refund confirmation to the customer.
  5. To confirm the updated refund status, the merchant sends a check status API request to
    Cybersource
     and includes the refund request ID. For more information, see Check Transaction Status.
  6. Cybersource
     sends a
    refunded
     status to the merchant.

iDEAL Workflow

This workflow describes the sequence of events that comprise a successful iDEAL transaction.
  1. The customer begins to checkout using iDEAL as a payment method and selects their bank.
  2. The merchant sends a sale API request to
    Cybersource
    . For more information, see Processing a Sale.
  3. Cybersource
     sends a
    pending
     status and a redirect URL to the merchant.
  4. The merchant redirects the customer to their issuing bank's website.
  5. The customer enters their payment information and is redirected to the merchant's success URL.
  6. The merchant displays payment confirmation to the customer.
  7. To confirm the updated payment status, the merchant sends a check status API request to
    Cybersource
    . For more information, see Check Transaction Status.
  8. Cybersource
     sends a
    settled
     status to the merchant.

iDEAL Refund Workflow

This workflow describes the sequence of events that comprise a successful iDEAL refund.
  1. The customer initiates a refund to the merchant.
  2. The merchant sends a refund API request to
    Cybersource
     and includes the sale request ID. For more information, see Refund a Payment.
  3. Cybersource
     sends either a
    pending
     or
    refunded
     status to the merchant.
  4. The merchant displays refund confirmation to the customer.
  5. To confirm the updated refund status, the merchant sends a check status API request to
    Cybersource
     and includes the refund request ID. For more information, see Check Transaction Status.
  6. Cybersource
     sends a
    refunded
     status to the merchant.

Merchant Account Types

There are two types of Cybersource merchant accounts,
Cybersource
 settlement services accounts
 and
processor direct contract accounts
.

Cybersource
 Settlement Services Account

This merchant account has no direct contract with a payment provider partner. The
Cybersource
 Financial Settlement Partner (FSP) collects funds on your behalf and settles them to your merchant account.
Cybersource
 requests the export compliance service for every transaction using the
Cybersource
 settlement services account. The export compliance service compares customer information to export control lists maintained by government agencies. If a customer's name appears on any government list, the transaction is declined.
To facilitate compliance checks for
Cybersource
 settlement services accounts, you must include these fields in your authorization service requests.
You must include these fields in the live environment to avoid receiving error messages.

Figure:

Mandatory Authorization Fields for a
Cybersource
 Settlement Services Account
billTo_city
billTo_country
billTo_firstName
billTo_lastName
billTo_street1

Processor Direct Contract Account

This merchant account must use the payment provider selected by
Cybersource
. If you have existing direct contracts, you must inform your sales representative.

Line Items

The Online Bank Transfer services use line items when you send a sale or refund request. Line items are used to include information about the goods that your customers purchase, such as product name, quantity, and price.
Line items are represented as the
item_#_
 fields, starting with
item_0_
, and increasing in numerical order.
These fields are required for each line item that you use:
item_#_productCode
item_#_productDescription
item_#_productName
item_#_quantity
item_#_unitPrice
Including Line Items in a Service Request
This example shows three valid line items.
<item id="0">
	<productCode>123456</productCode>
	<productDescription>Red</productDescription>
	<productName>Shirt</productName>
	<quantity>1</quantity>
	<unitPrice>30.00</unitPrice>
</item>
<item id="1">
	<productCode>456789</productCode>
	<productDescription>Green</productDescription>
	<productName>Pants</productName>
	<quantity>3</quantity>
	<unitPrice>19.99</unitPrice>
</item>
<item id="2">
	<productCode>987654</productCode>
	<productDescription>Blue</productDescription>
	<productName>Dress</productName>
	<quantity>2</quantity>
	<unitPrice>25.50</unitPrice>
</item>