SEPA
Overview
Key information | |
|---|---|
Payment type | Direct Debit |
Integration | Sync, Async, Checkout, Payment Link (API only) |
Countries | AT, BE, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GR, HU, IE, IT, LT, LU, LV, MT, NL, NO, PL, PT, RO, SE, SI, SK |
Languages¹ | en |
Processing currencies | EUR |
Settlement currencies² | EUR, GBP, USD, AUD, CAD, CHF, DKK, HKD, JPY, NOK, NZD, PLN, SEK |
¹ The display language is controlled by the bank interface. It cannot be set by the merchant.
² Please contact Payvision Sales to confirm any settlement currency exceptions
Supported features
- Mail Order
- Telephone Order
- Sandbox
- Chargebacks
- Fraud³
- Autovoider⁴
- Device Optimization
####Additional features:
- Timeout⁵: 1800 seconds
- Transaction amount range: defined by the consumer's payment institution. Payvision can put a MAX amount based on risk analysis.
PLEASE NOTE:
Features described are supported by the platform but individual connectors (acquirer/bank) may only support a subset of these features. You can check the connector sheets for full details.
³ Fraud: account takeover fraud is the only possibility. Fraud Scrubbing (ACEProtect): Basic rule-based fraud prevention rules can be enabled.
⁴ Autovoider: Supported, used in case of File Generation service communication problem.
⁵ Session timeout is the time when the consumer is redirected to his bank and his session getting expired at his bank.
Available workflows
Workflow | Supported | Comments |
|---|---|---|
Authorize → incremental authorize | 🗵 No | |
Authorize → cancel | 🗹 Yes | |
Authorize → partial cancel | 🗵 No | |
Authorize → capture | 🗹 Yes | |
Authorize → partial capture | 🗹 Yes | |
Authorize → partial capture → partial capture | 🗵 No | |
Authorize → capture → refund | 🗹 Yes | |
Authorize → capture → partial refund → partial refund | 🗹 Yes | |
Authorize → capture → recurring | 🗹 Yes | |
Credit | 🗹 Yes | Blind credits supported. |
Payment | 🗹 Yes | |
Payment → refund | 🗹 Yes | |
Payment → partial refund → partial refund | 🗹 Yes | |
Payment → recurring | 🗵 No |
Integration notes
Required parameters
Sync transactions
The minimum required parameters for a sync transaction are:
Parameter | Example value |
|---|---|
header.businessId | {your_business_id} |
action | authorize |
transaction.storeId | {your_store_id} |
transaction.brandId | 6010 |
transaction.amount | 1.00 |
transaction.currencyCode | EUR |
transaction.trackingCode | {your_tracking_code} |
bank.iban | AT152011128161647502 |
bank.accountHolderName | John Doe |
bank.mandateId | DE23100000001234567890 |
bank.dateMandateSigned | 2018-08-03 |
Async transactions
The minimum required parameters for an async transaction are:
Parameter | Example value |
|---|---|
header.businessId | {your_business_id} |
action | authorize |
transaction.storeId | {your_store_id} |
transaction.brandId | 6010 |
transaction.amount | 1.00 |
transaction.currencyCode | EUR |
transaction.trackingCode | {your_tracking_code} |
transaction.returnUrl | {your_return_url} |
bank.iban | AT152011128161647502 |
bank.accountHolderName | John Doe |
Mandate information
For dateMandateSigned and dateCollected, please ensure you either provide a valid date value or no value at all for these fields.
Parameter lengths
Parameter | Length | Comments |
|---|---|---|
bank.mandateId | 35 characters max | This is the Unique Mandate Reference (UMR) and must comply with the following requirements:
|
Contact us
Have a question? Contact us.
Updated about 1 year ago