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:

Bancontact

{
     checkout_id <string>: Optional reference to a checkout object
     redirect_url <string>: The return url to which the customer is redirected after an approval
}

Creditcard

{
     checkout_id <string>: Optional reference to a checkout object
     redirect_url <string>: The return url to which the customer is redirected after an approval
     force_3DSecure <boolean>: Force 3D Secure on this transaction
     capture_now <boolean>: Whether auto-capture or not. Defaults to 'true'. Setting the boolean to 'false' will only authorize the transaction
     card_holder <string>: Cardholder's name
     card_token <string>: Card token. For performing a transaction based on a card token. The fields card_holder, card_token, card_cvv and card_expiry_month and card_expiry_year are required
     card_cvv <string>: Card CVV. Please be aware that due to PCI compliance you're never allowed to store the CVV
     card_expiry_month <integer>: The card expiry month
     card_expiry_year <integer>: The card expiry year
}

CreditClick

{
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after completing/aborting the transaction.
}

Directdebit

{
     account_type <string>: The type of the account used for the transaction
     bank_account <string>: The bank account token ID
     check_number <string>: The number of the check used (used in case of ACH, and it's optional)
     order_source <string>: The source of the order (This is field is Vantiv specific as far as we know)
     type <string>: Type of direct debit transaction
}

Giropay

{
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after completing/aborting the transaction
}

iDEAL

{
    issuer <string>: The issuer's identifier
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after an approval
}

Klarna

{
    goods_list <array>:
        goods_list.discount <number>
        goods_list.flags <array>
        goods_list.price <number>
        goods_list.quantity <number>
        goods_list.reference <string>
        goods_list.vat <number>
    pclass <number>: The ID of the associated PClass
}

Paypal

{
    description <string>: Payment description, displayed on the PayPal page. Maximum characters: 127
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after an approval
    capture_now <boolean>: Whether auto-capture or not. Defaults to 'true'. Setting the boolean to 'false' will only authorize the transaction
}

Paysafecard

{
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after completing/aborting the transaction
}

Sepa

{
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after an approval
    bank <array>: SEPA bank details for transaction
        bank.account_number <string>
        bank.bank_code <string>
        bank.country_code <string>
        bank.holder_name <string>
}

Sofort

{
    checkout_id <string>: Optional reference to a checkout object
    redirect_url <string>: The return url to which the customer is redirected after completing/aborting the transaction
}