Reverse Payments

Yapily's knowledge article about Reverse Payments

Reverse Payments is a feature from the Open Banking API Specification V3.1.5. Reverse Payments allows a TPP to request that the refund account information be included as part of the payments response. By returning the refund account information (i.e. name, sortCode and accountNumber), the TPP is then able to initiate a further payment to refund the original payment, if required.

In order to retrieve the refund account information, a TPP must specify readRefundAccount=true when executing a payment authorisation request on any of the POST Create Payment Authorisation Request endpoint.


As of 24th November 2020, this feature is currently only supported for payments with the following payment types:


And for the following banks:

  • NatWest
  • RBS
  • Ulster Bank NI

Barclays, Nationwide, and Dankse will be released soon and it is expected many UK banks with follow suit.


Any Institution that supports reverse payments will first have the feature READ_DOMESTIC_SINGLE_REFUND when executing GET Institution. If an Institution supports reverse payments, you may request refund account information by adding an additional parameter, readRefundAccount to the POST Create Payment Authorisation Request (line 7):

    "applicationUserId": "{{application-user-id}}",
    "institutionId": "{{institution-id}}",
    "callback": "{{callback-url}}",
    "paymentRequest": {
            "type": "DOMESTIC_PAYMENT",
            "readRefundAccount": true,
            "paymentIdempotencyId": "{{paymentIdempotencyId}}",
            "reference": "{{paymentReference}}",
            "contextType": "PERSON_TO_PERSON",
            "amount": {
                "amount": "{{paymentAmount}}",
                "currency": "{{paymentCurrency}}"
            "payee": { ...

The response for the authorisation will confirm that the feature is supported by the Institution and is being actively used for this particular payment consent (see line 12 within the featureScope property):

    "meta": {
        "tracingId": "7e36098c464cad866f01c6e08bf8163f"
    "data": {
        "id": "b81ba80d-cc77-4e78-b90e-7060c0c8254a",
        "userUuid": "c3fb97e0-44e2-477b-bfdc-c2534057b5e9",
        "institutionId": "rbs",
        "status": "AWAITING_AUTHORIZATION",
        "createdAt": "2020-10-06T13:27:26.162Z",
        "featureScope": [
        "authorisationUrl": "",
        "qrCodeUrl": ""

If the readRefundAccount property is NOT supported for either the payment type or the Institution, the following error message will be returned:

    "error": {
        "code": 400,
        "tracingId": "64efa35a974eeb5107dcbe968b7f8e9b",
        "status": "BAD_REQUEST",
        "source": "YAPILY",
        "message": "Read Refund Account is not supported for this payment type. We can help you on"
    "raw": [],
    "monitoring": []

Assuming that the authorisation request is successful and the user provides consent for the payment, use the consentToken to execute POST Create Payment Request and the response should also include the readRefundAccount object (lines 3-15 below):

    "createdAt": "2020-08-05T11:02:13.819Z",
    "refundAccount": {
        "name": "BLOGGS JOE",
        "accountIdentifications": [
                "type": "ACCOUNT_NUMBER",
                "identification": "12345678"
                "type": "SORT_CODE",
                "identification": "040065"
}, ...

readRefundAccount should also be present in the response from GET Get Payment Details if refund account details were requested.

If the readRefundAccount parameter is omitted from a payment request, it will be set to false by default and no refund account information will be returned even if the Institution supports reverse payments.