Recurring Payments
Beam supports recurring payments and subscription billing. If you need to charge a customer’s saved card without them being present — for renewals, installments, or top-ups — CIT/MIT is the feature for you.
CIT/MIT must be enabled on your merchant account before you can use it. Please contact us for review and approval.
Card networks (Visa, Mastercard) require you to flag each transaction correctly so recurring and stored-card payments are processed under the right rules.
- Customer-Initiated Transaction (CIT) — the cardholder is present and actively triggers the payment. For example, a shopper checking out, or saving their card on file and approving the first payment.
- Merchant-Initiated Transaction (MIT) — the merchant charges a stored card without the cardholder being present. For example, a subscription renewal, an installment, or a delayed/top-up charge.
Network Transaction ID (NTI)
Network Transaction ID (NTI) is a unique identifier assigned by the card network to a transaction. The NTI from
the initial CIT links subsequent MITs back to the original cardholder-approved payment, so the network treats the
whole series as one agreement.
How CIT and MIT work together
CIT comes first and produces an NTI; every later MIT must reference that NTI.
Guides
- How Beam Supports CIT/MIT — integration details and prerequisites.
- Customer-Initiated Transactions (CIT) — run the initial transaction and capture the NTI.
- Merchant-Initiated Transactions (MIT) — charge a stored card using the NTI.
- Network Response Codes — interpret
iso8583ResponseCodeandmerchantAdviceCodeon declines.