Used to initiate the authorisation process and direct users to the login screen of their financial Institution in order to give their consent for Sweeping Variable Recurring Payments. The request would return an Authorization URL and an Identifier for the consent created at the Institution. First make sure that the payment feature you wish to execute is supported by the bank by checking the features array in GET Institution.
Features:
INITIATE_DOMESTIC_VARIABLE_RECURRING_PAYMENT_SWEEPINGUse HTTP Basic Authentication with your Application ID as username and Application Secret as password. Manage credentials in the Yapily Console. See Authentication for details.
Mandatory. The reference to the Institution which identifies which institution the authorisation request is sent to.
"yapily-mock"
Define the restrictions and limits for payment orders as part of Sweeping VRP consent
Mandatory. The payment initiation object defining the details of the payment under the Variable Recurring Payment consent.
This is the Yapily user identifier for the user returned by the create user step POST ../users
A client's own user reference. If the client wants to work with their own unique references for individual PSUs then they can use the applicationUserId property to provide that value. Where Yapily does not already have a Yapily userUuid that matches the supplied applicationUserId, then a new Yapily userUuid is created automatically and linked to the applicationUserId value. Clients can then use either their own applicationUserId or the Yapily userId to reference the same user in future calls.
Extra parameters the TPP may want to get forwarded in the callback request after the PSU redirect.
Optional. The server to redirect the user to after the user complete the authorisation at the Institution.
See Using a callback (Optional) for more information.
"https://display-parameters.com"
Optional. The server to redirect the user to after the user complete the authorisation at the Institution.
Conditional. Used to receive a oneTimeToken rather than a consentToken at the callback for additional security. This can only be used when the callback is set.
See Using a callback with an OTT (Optional) for more information.
false
Conditional. Information needed to complete compliance checks. Mandatory for Yapily Connect customers.