Transmitting user consent

As a PSD2-compliant bank Elavon requires user consent to accept payment initiation from a PISP.

Note: For new customers, the Bank-initiated flow, where the transfer token is automatically redeemed, is set as the default.

For banks that support the ability to initiate payments using token redemption by the TPP, TPP-initiated (2-step) flow, please see Optional features.

Elavon requires the TPP to explicitly confirm customer consent by redeeming the transfer token with a POST /transfers call. This is referred to as a TPP-initated (2-step) flow.

For 2-step payments, the TPP receives a tokenId in response to the transfer request.

TPP-initiated Payments (2-step)

The basic flow looks like this (click to enlarge):

Note: If you would prefer to use the auto redeem functionality to automatically redeem authentication tokens for 2-step payments, see Optional features for more information.

Guidance on how to structure and when to make the corresponding API calls is discussed under the respective payment type: