Skip to content
Last updated

VRP consent status

The following table describes the possible statuses that can be returned in the status field of the POST /vrp-consents, GET /vrp-consents and GET /vrp-consents/{id} endpoints.

StatusDescription
AUTHORIZEDThe VRP consent setup request has been authorized by the bank.
PENDINGThe VRP consent setup request has passed Token.io's validation. If you are using HP and the VRP confirmation page is turned on, the VRP setup success page will be shown with status set as PENDING.
PENDING_MORE_INFOThe VRP consent setup request lacks mandatory fields (e.g., bankId) that have to be collected before connecting to the bank. If you are using HP, Token.io may be waiting for the user to enter the required information. If you are not using HP, this is a non-recoverable state and you must populate the required information in a new POST /vrp-consents call.
PENDING_REDIRECT_AUTHThe VRP consent setup request has been acknowledged by the bank and Token.io is awaiting user confirmation at the bank's page. If HP is in use and the VRP confirmation page is turned on, the VRP setup success page will be shown with status set as PENDING.
PENDING_REDIRECT_AUTH_VERIFICATIONToken.io has received the bank callback information and is currently verifying it with the bank. If you are using HP and the VRP confirmation page is turned on, the VRP setup success page will be shown with status set as PENDING.
REJECTEDThe VRP consent setup request has been rejected. More details are shared in the corresponding status reason information. This status will be set whenever an unrecoverable error happens during the flow.
FAILEDToken.io failed to proceed with the VRP consent setup request due to problems reaching the bank or the user abandoning the flow (all PENDING statuses are turned into FAILED 30 minutes after VRP consent setup request).
REVOKEDThe status indicates the VRP consent has been revoked. The user has potentially revoked consent through a different channel.

If you have any feedback about the developer documentation, please contact devdocs@token.io