This page provides an overview of the payments methods provided by the SepaExpress adapter in the IXOPAY platform. It also includes a full list of all configuration options available to you when integrating SepaExpress within your payments landscape, as well as an overview of the parameters required when submitting a transaction via IXOPAY's API.
|Payment Method||Transaction Flows||Transaction Types|
|DirectDebit||iFrame Form & Server-To-Server||Debit, Register, Deregister, Refund|
|CreditTransfer||iFrame Form & Server-To-Server||Payout|
Depending on your setup SepaExpress can be used as Server-to-Server only integration, or with an iFrame Payment form.
For the Server-to-Server integration the IBAN must be sent within the customer details, otherwise the customer will enter its IBAN within the iFrame form.
If your merchant is configured to generate and verify the SEPA mandate on the Gateway, a redirect to the iFrame Payment Page is always required.
Otherwise, it can be only server-to-server communication, and you provide all information as described in Additional parameters below.
additionalId1: must contain the Order ID. One Order ID can contain more than one transaction! Relevant for SepaExpress to detect the sequence of the transaction and for refunds. Allowed pattern
additionalId2: for recurring transactions it must contain the Contract ID: A unique identifier of the user or contract of the user on merchant level. One Contract ID can contain more than one Order IDs! Relevant to detect the sequence of the transaction.
customer.iban: mandatory (for Server-to-Server)
customer.mandateId: mandatory. Allowed pattern
Make sure to use the
ibanCustomer element within the XML instead of the normal
customer object. The ibanCustomer contains the fields necessary for DirectDebit