PSD2: Payment Initiation

In addition to single SCT payments, Unifiedpost Payments also supports bulk SCT payments. The requests and processes are very similar, only the single SCT payment will be described here.

‍

1. Execute ./payment.sh or ./bulk-payment.sh to submit a POST to /external/psd2/v1/payments/sepa-credit-transfers
2. You will receive a JSON response (example below).
3. You should  store the status URL and the paymentId and redirect the PSU's browser to the scaRedirect.
4. The PSU will be presented with details of the payment and be asked to approve the payment. This is normally done in a mobile app but in the sandbox environment can be done from the web page by clicking on the "fingerprint" of the PSU: eith erJohn or Emma. Cancel is also an option.
5. In all cases, Unifiedpost Payments will redirect the PSU's browser to the URL provided in the header TPP-Redirect-URI  of the original request.  Note in the scripts we set a dummy URL for the sandbox but it must be a URL at the TPP so the PSU can continue the process. You should set some identifying identifier in the URL, to be able to link this callback with the original request the shell script uses the X-Request-Id) but you are free to choose any other unique identifier.
6. Make a call to the status URL to obtain the status of the payment. In the example the status is ACTC which indicates that the PSU has authorised the payment and it is successfully validated but it has not yet been successfully executed. See "Supported Payment Initiation Statuses"to see the list of statuses we support.
7. See to see the PSUs and the IBANs supported in the sandbox: psd2-sandbox-general

‍