Recurring payment status updates

Receive updates on recurring payments as their status changes

The time it takes a bank to process a RPIRRPIR - Recurring Payment Initiation Request can vary and may not be instant. Because of this, Vyne provides updates when the status of a recurring payment changes.

There are different methods to obtain the status of the recurring payment.



Use case

Callback URL payload

A payload appended to the callback URL - the URL a consumer is redirected to after they have completed a payment.

Presenting an immediate confirmation to the consumer at the end of the payment flow. The payload allows the merchant to display a success or failure message (for example, if payment is cancelled by the consumer).

Get payment status

Get the status of the payment manually.

If a manual update is required on demand, merchants can get the status of the payment at any time.

Approach 1: Callback URL payload

After the consumer authorises the payment at their bank, you should direct them to a confirmation page. For every RPIRRPIR - Recurring Payment Initiation Request, you'll need to provide a callbackUrl parameter. Vyne redirects the consumer to the callbackUrl at the end of every payment flow, regardless of the payment's outcome.

In order to allow merchants to provide consumers with feedback reflecting the payment status, Vyne provides payment information in a payvyne_payment_payload parameter appended to the callbackUrl. payvyne_payment_payload includes paymentId and paymentStatus as claims in a Base64 encoded JWT token.

Encoded URL


  "kid": "aeaf334e-9a54-41e8-961a-e3838081fd5c",
  "alg": "RS256"
  "jti": "46406996-1a33-4eef-a891-25077a576676",
  "iss": "",
  "sub": "payment_info",
  "paymentStatus": "COMPLETED",
  "paymentId": "787fd82e5578fc3b",
  "iat": 1608226143,
  "exp": 1608227943

Token integrity

The integrity of the token can be verified by using either one of the industry standard libraries provided by, corresponding to your platform's programming language. Verification can be done by using one of the public keys exposed by Vyne.

Approach 2: Get request status

You can request a status update on any payment at any time by sending an HTTP GET request to the relevant base URL + /api/v1/recurringPayments including the headers Authorization: Bearer <payment_token>. Generate a fresh payment token for the <payment_token>.


curl --location --request GET '<paymentId>' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <payment_token>'

Request parameters




The requestId from the initiation response


    "id": "a5630672241cf824",
    "amount": "1.00",
    "currency": "GBP",
    "description": "test payment",
    "status": "COMPLETED",
    "bank": "Monzo",
    "destinationAccount": "GBP1",
    "firstPaymentDate": "2026-09-16",
    "frequency": "MONTHLY",
    "numberOfPayments": 2,
    "createdAt": "2021-09-27T10:11:09.089",
    "updatedAt": "2021-09-27T10:11:58.424",
    "customerReference": "jgdw74jg",
    "merchantReference": "yegdt6t67g"

Request statuses

Recurring payment requests can be in one of many statuses which reflect the stage in the process the payment has reached between Vyne and the bank. Find out more about payment statuses here.


Helpful to know

The latest API keys can be found at the relevant base URL + /api/keys/.

Choosing the right key for verification is done by using the kid (key ID) attribute from both the JWT header and the exposed keys.

What’s Next

Now you've successfully got updates for your recurring payment requests, learn how to test your integration.

Did this page help you?