This functionality is for the following PSPs:
Nets Easy (TP48276 / 2022.4003-T)
Netaxept (TP48880 / 2023.0504-T)
Billwerk+ (formerly Reepay)
Future or new forbidden response codes are updated continuously in BRP and could depend on any new regulations or changes from PSPs. Changes can expected from Nets Easy and NetAxept.
Invalidating a mandate
When a payment attempt done with any of the Nets payment services return a response code that indicates that the card is stolen, lost or for any other reason should never be used again, BRP will invalidate the RCP mandate. This is done by setting the expiration date to yesterday.
Informing the customer
If the follow up point “Missing valid credit card consent” is enabled, the customer will receive information that their RCP mandate is expired and asked to add another card.
Logs
The error codes are shown both in the invoice list and when viewing an invoice. “0” usually means no error. Click the invoice to view the full error message.
The invoice history will show error codes and the card consent history will show if the card consent (RCP mandate) was invalidated because of a forbidden error code.
Information from Nets
Nets Easy:
Nets has for Nets Easy recommended to only permanently block for error codes (04, 14, 15, 41, 43, 46, 54, 57) on the following link , listed under “Re-attempt can be forbidden”: https://developers.nets.eu/nets-easy/en-EU/docs/manage-subscription-retries/
This was confirmed with Nets again on 10th of January 2024.
Netaxept:
For NetAxept, BRP also follows Nets guidelines to permanently block “CF” and “PB”.
Response and error codes from Netaxept and Issuer: https://developer.nexigroup.com/netaxept/en-EU/docs/response-codes/
Forbidden error code “CF” was scheduled to be implemented in Netaxept production environment in 2023, but was postponed without any new release date.
Forbidden error code “PB” was scheduled to be added in Netaxept production environment on 2024-01-25. BRP added “PB” in versions 2024.0202 (GA02) and 2023.410352 (GA41).
Billwerk+
Billwerk+ (formerly Reepay) will, in case of a charge error, reply with both “Error state” and “Error code”
API documentation which lists a few soft_declined and hard_declined (error state) examples https://reference.reepay.com/api/#testing
BRP will invalidate RCP mandates if a charge attempt gets error state “hard_declined”. In other words it will be permanently blocked for future RCP attempts until the customer registers a new card.
“soft_declined” will not block any future attempts in BRP. Error code is saved in BRP invoice history and error state is visible in the Billwerk+ portal when viewing the transaction.