Initiating a recurring payment with the Webview
In this guide, we will create and validate a recurring payment using the Pay product.
Last updated
Was this helpful?
In this guide, we will create and validate a recurring payment using the Pay product.
Last updated
Was this helpful?
This feature must be enabled by your commercial contact.
Note that this guide assumes you have the following information on hand:
A Powens domain with Pay enabled.
A Powens domain client with client identifiers, thereafter named clientId and clientSecret.
A URL to redirect the end user to at the end of the process, registered with the client, thereafter named redirectURL.
An optional state that will be transmitted to your redirect URL, thereafter named optionalRedirectState.
Recurring payments are payments executed periodically by the bank. Once initiated, the bank will create instances of the recurring payment according to the provided schedule, without the need for the end user to validate the execution.
The basic initiation workflow is the same as in , with the following notable differences:
The payment object only contains one instruction, with the execution date type being "periodic", and additional properties representing the schedule to be set.
The payment status needs to be interpreted differently.
The basic initiation workflow will be the following:
In order to create recurring payments, we need a special access token with the payments:admin scope, obtained using client credentials:
You can now create a recurring payment request with the following request:
The following are examples of different identity kinds with Pay:
Now that you have the recurring payment validation token, you can create the webview URL by taking the webview URL and adding the following parameters to it:
domain: your client domain.
client_id: the client identifier for your application (clientId).
redirect_uri: the same redirect URL you've used when creating the recurring payment (redirectURL).
state: the same state you've used when creating the recurring payment (optionalRedirectState).
code: The scoped token you've generated on your previous request to the API.
payment_id: the identifier of the recurring payment.
This will make you obtain a URL of the form:
You can redirect your payer to this URL.
Once the payer has either completed the recurring payment validation flow, or has cancelled from either our Webview or the bank's interface, they will go on the callback URL you have configured on the payment with the following parameters:
state: the optional client state you have configured on the recurring payment, i.e. {optionalClientState}.
id_payment: the identifier of the recurring payment that the user comes from.
error (optional): set to "cancelled" if the payer has cancelled the recurring payment from our Webview.
error_code (optional): set to the recurring payment's error code, if the payment has been cancelled or rejected by the bank.
bank_message (optional): set to the bank message, if available.
payment_state (optional): the state of the recurring payment, if the payer has been redirected by the bank.
During and after the initiation of a recurring payment, you may want to check on the status of said recurring payment, or to get data back from the recurring payment initiation request.
Webhook events will only be triggered during a background refresh / synchronization of the recurring payment's state.
This method is not recommended for polling the recurring payment's status regularly, it is recommended to wait for incoming webhook events to this end.
However, it is recommended for when receiving a callback regarding a recurring payment from an end user, or for debugging purposes.
In the resulting recurring payment resource, you are to get the state property, and do the following:
If the status is pending, it is currently active and being executed periodically.
If the status is expired, it means that the recurring payment will not be updated anymore.
If the status is accepted, it means that the initiation was successful but the bank will not provide further updates; if you accept the risks, you can consider the recurring payment as active or done.
If the status is done, it means that all required executions have been done.
If the status is rejected, it means that the recurring payment has been rejected by the bank, or stopped by the end user through the bank.
See for more information.
A payer_identity for the recurring payment request and a beneficiary_identity for every instruction are required and must contain information on either the payer (which you redirect to the webview) or the beneficiary (matching the routing information). For the definition of such objects, see the definition.
See the and for more information on the payload or returned information.
In order for the payer to be able to validate the recurring payment request, you first need to create a token scoped to validate the created recurring payment specifically. You can do this using the token created in :
See the for more information.
For security reasons, following such a callback from the payer, it is recommended to check the recurring payment's state manually; see .
In order to receive updates when a recurring payment switches states, it is recommended to and wait for events regarding recurring payments.
For more information, see in the Payments API reference.
In order to get a given recurring payment's status, you can call the GET /payments/{id} endpoint, with the identifier of the recurring payment. See for more information.
A recurring payment with the accepted status could still be rejected by the bank (e.g. for insufficient funds at execution time), however we can no longer poll the recurring payment's status on our side. If you want to avoid such cases, you can identify connectors with this behaviour by checking the partial_status_tracking property of connectors; see .
See the definition for reference.
