Plan customer and merchant initiated payments
Separate saved-method storage from consent and later billing behavior.
Choose who controls billing
Use the gateway recurring module for supported fixed schedules, or design a custom orchestration layer when your application controls timing. Saving a method alone does not define the subsequent billing relationship.
Track customer participation
Keep the initial storage transaction and later customer-initiated or merchant-initiated actions distinct. Flow Application responsibility Initial storage Record consent and the initial approved transaction Customer initiated Customer participates; evaluate authentication requirements Merchant initiated Reference the agreed stored-credential relationship without an interactive challenge
Verify the request contract
The narrative source includes parameter forms that differ from current REST examples. Confirm the selected endpoint schema and processor requirements before sending credential-on-file indicators. Design guidance only: this page intentionally does not present an unverified combined CIT/MIT request as runnable code.
Test the lifecycle
Retain the initial gateway identifier, consent and customer-to-merchant mapping. Review retries, cancellation, updated payment methods and authentication requirements with the integration team before launch.