Subscription product in the EU. First payment went through 3DS, the card was tokenized, and every renewal after that was a plain POST to the charge endpoint with the token and an amount. It worked, so nobody touched it.

Then renewal approval sat at 71% while first payments sat at 90%. The decline codes were not 54 or 14. They were soft declines asking for authentication (Visa 1A), on cards that were fine.

The cause: from the issuer's side, our renewals were ordinary e-commerce transactions with no cardholder present and no 3DS. Nothing told them this was a merchant-initiated charge under an agreement the customer had already authenticated. We never sent a stored-credential indicator, and we never referenced the network transaction ID from the first payment.

The fix was three fields, not a rewrite:

  1. Mark the first payment as the customer-initiated one that stores the credential.
  2. Save the network transaction ID from its response, next to the token.
  3. Mark every renewal as merchant-initiated recurring and send that saved ID with it.

Renewal approval went from 71% to 88% in two billing cycles. We changed nothing else.

The annoying part is that the sandbox never complained. It approves everything with a token.

Does your gateway store the original transaction ID for you, or do you have to keep it yourself? We had to keep it ourselves, and I'd like to know how common that is.

Payneteasy handles this kind of payment flow for merchants and PSPs — see how it works.