Understand the role of the original network transaction ID in distinguishing cardholder-initiated versus subsequent recurring transactions across Visa and Mastercard

Verified steps

1. Card networks require that the first transaction in a recurring series (the CIT) produce a network transaction identifier (variously called the network transaction ID, trace ID, or original transaction reference) in the authorization response
2. This ID must be stored by the merchant or their PSP and submitted in subsequent MIT authorizations as proof that the relationship began with a properly authenticated CIT
3. Visa's MIT framework requires the Visa Transaction Identifier (VTI) from the original CIT be passed in the subsequent authorization request under the appropriate field; Mastercard uses a similar concept with its own trace reference
4. PSPs like Stripe handle this automatically when you use stored PaymentMethods and off_session=true; verify via Stripe's documentation whether and how the network transaction ID is surfaced or if you need to pass it explicitly
5. For direct acquirer integrations, retrieve the network transaction ID from the first authorization response message field and store it in your payment record; include it in the subsequent authorization request per the network specification
6. Test with a Visa and a Mastercard to confirm both networks return and accept the transaction ID in your integration, as the fields differ