Do recurring payments survive a card being reissued?
When a card expires, is replaced or is reissued, the scheme updates the corresponding network token, and subsequent charges keep running on it. The token captured on the first customer-initiated payment is stored in the NORBr Vault as a universal token, reusable across every provider configured on the merchant account, so each following charge reuses it directly.
In detail
With network tokenization, yes in most cases. When a card expires, is replaced or is reissued, the scheme updates the corresponding network token, and subsequent charges keep running on it.
How it works
The token captured on the first customer-initiated payment is stored in the NORBr Vault as a universal token. It is reusable across every provider configured on the merchant account, so each following charge reuses it directly, whichever provider routing selects.
When the issuer replaces the card, the network token stays valid and points to the new card details. The merchant does not need to ask the customer for new card data, and the subscription continues without interruption.
When a charge still fails
A failed recurring charge follows the routing and fallback logic configured for the merchant account. If it still fails, a Retry policy takes over, with scheduled attempts, and the subscription can then be left past due, paused or canceled according to the rules of its Offer.
Why it matters for your merchants
Card reissuance is a routine source of involuntary churn for subscription businesses. Keeping tokens updated at scheme level reduces that churn without extra work for your merchants or their customers. The token fields and the tokenization dashboards let them follow how many charges ran on network tokens.