As part of the Open Banking framework for Payment Initiation Service Providers (PISPs), Adyen provides PISP endpoints to initiate payment transactions on behalf of users who have granted their consent.
Use your access token to authenticate your requests to the /payments endpoint.
Initiate a payment
To initiate a single payment on behalf of your user, make a POST /payments/target-2-payments request. Provide the following parameters in the request body:
| Parameter | Description |
|---|---|
instructedAmount |
The currency and the amount of the payment. |
creditorAccount |
The account number of the creditor—the person or entity who will receive the payment. |
debtorAccount |
The account number of the debtor. |
creditorName |
The name of the creditor. |
creditorAddress |
The address of the creditor. |
Here's an example of a request to initiate a payment of EUR 0.50 to Railway Company.
The response contains the details of the initiated payment, including the transactionStatus and the paymentId.
| Parameter | Description | |
|---|---|---|
transactionStatus |
Current status of the payment. Possible values: ACCP, ACFC, ACCC, ACSC, ACSP, ACTC, ACWC, ACWP, CANC, RCVD, RJCT, PDNG, PART, PATC. |
Get payment status
To get the status of the payment, make a GET /payments/target-2-payments/{paymentId} request. This endpoint is intended to be polled to determine whether the user confirmed the payment.
The response may look like this:
Get authorisation status
To get information about the payment authorisation, make a GET /payments/target-2-payments/{paymentId}/authorisations/{authorizationId} request, where paymentId represents a unique identifier for a payment transaction and authorizationId is a unique identifier for a specific payment authorisation.
The response contains the authorisation status.
| Parameter | Description |
|---|---|
scaStatus |
Status of authorisation. Possible values: received, psuIdentified, psuAuthenticated, scaMethodSelected, started, unconfirmed, finalised, failed, exempted. |