Transaction details

Different types of transactions have a lot in common, although they can vary in some parts. To tackle this issue, transactions are embedded with a Transaction Details schema which depends on the type of payment product used to process the transaction. This can also be seen in the POST /transaction/start call.

For more information about additional merchant data click here.

The following sections show the different details types available:

Dummy

{
    checkout_id <string>: Optional reference to a checkout object
    dummy_outcome <string>: If set, the transaction is directly updated to this transaction status
    dummy_outcome_update <string>: If set, the transaction will be updated to this transaction status
    redirect_url <string>: The return url to which the customer is redirected after completing/aborting the transaction
}

Sepa

{
    sender <array>: SEPA sender details for transaction
        account_number <string>
        bank_code <string>
        country_code <string>
        holder_name <string>
    checkout_id <string>: Optional reference to a checkout object
    mandate <string>: SEPA mandate reference
    mandate_date <string>: Date when the SEPA mandate was signed (YYYY-MM-DD)
    sepa_due_date <string>: SEPA due date (YYYY-MM-DD)
    redirect_url <string>: The return url to which the customer is redirected after an approval
    recurring_id <string>: Recurring identifier
}