Library · Subscriptions · How to run this
The rebill has to point at the original sale
The first bill is the one the shopper was present for. They typed the card, used a wallet, or passed a challenge. The issuer filed a receipt for that sale.
Every later bill happens without them. Processors call the first sale CIT and the later bill MIT. The names do not matter. What matters is that the later bill points at that receipt. If it does not, the issuer sees a brand-new card-not-present charge. The shopper is not there to prove it. Declines and “I don’t recognize this” follow.
Pair: Rebill original-sale checklist on Subscriptions. The day list after a fail is a different job: Dunning by decline family. This page is the chain, not the approval-rate split.
What the later bill has to carry
The original sale was shopper-present. Checkout, wallet, or a challenge they completed. A customer-service key-in with no receipt is a weak first sale. Later bills inherit that weakness.
The gateway stored the receipt. Not only the card token in the CRM. The token says “we can hit this PAN.” The receipt says “this PAN already approved a first sale with this merchant.”
The rebill sends that receipt. If the gateway call only sends the token, the issuer has nothing to chain. Ask the gateway, on one failed rebill, whether the original ID went out. If they cannot show it, the chain is already broken.
Same merchant account, or a documented handoff. Moving volume to a new account usually drops the receipt. The new account then bills a “first sale” with nobody at checkout.
A replacement card still points back. Account updater can swap a PAN or expiry. The replacement has to stay tied to the original sale. Billing the new PAN as a fresh checkout is how you kill continuity to “fix” updater.
After you tick the list
If the original ID is missing, stop spraying dunning. You are not going to recover those bills with more days. Fix the store of the receipt, or take a new shopper-present sale.
If you cannot look up the original ID on a failed rebill, you cannot run continuity on that gateway. That is the hole.
Do not paste gateway field names into the CRM and call the chain healthy. Tick the jobs. Then bill.
Related: MIDs (the account that must still hold the receipt), Payment orchestration (a hop is not a new first sale), Chargebacks (unrecognized later bills).
Procedure
- Confirm the original sale was shopper-present.
- Confirm the gateway stored that receipt, not only the token.
- On one failed rebill, ask whether the original ID went out.
- If the account changed, confirm the new account received the chain.
- If a PAN was replaced, keep it pointed at the original. Then bill.
Failure modes
- Treating a CRM card token as the original receipt.
- Starting continuity on a customer-service key-in with no stored ID.
- Moving the rebill to a new merchant account and billing it as a first sale.
- Billing an updater replacement PAN as a fresh checkout.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Shopper-present sale
- The first bill the cardholder was there for. Checkout, wallet, or a challenge they finished. Processors call this CIT.
- Later bill
- A charge without the shopper at the keyboard. It has to carry the original sale’s receipt. Processors call this MIT.
Work with us — We run this job on your accounts. Services
FAQ
- Is a card on file enough to rebill?
- No. The issuer needs the original shopper-present sale’s ID. A CRM token without that receipt looks like a new card-not-present charge.
- Can I start a subscription from a keyed customer-service sale?
- Only if that first sale still counts as shopper-present with a stored receipt. A CS key-in with no original ID will fail later bills.
- Does moving the bill to a new merchant account keep the chain?
- Not unless that new account received the original receipt. A fresh token on a new account is a new first sale.