When processing a payment where the card details were provided by the cardholder via phone or mail (not through an online form), set payment_method_options.card.moto to true on the PaymentIntent
MOTO transactions are explicitly exempt from SCA requirements under PSD2; setting this flag signals to Stripe, the issuer, and the network that SCA was not required for this transaction type
Create the PaymentIntent server-side with the card details provided via your PAN entry interface (a manual virtual terminal or operator-entered card data); ensure your integration is PCI compliant to handle raw card data
The MOTO flag affects ECI and other authorization fields; verify with your acquirer that MOTO transactions appear correctly in settlement and reporting
Do not set moto=true for online card-not-present transactions; it is strictly for operator-entered telephone or mail-order scenarios
Test MOTO transactions in Stripe's test mode using test card numbers and confirm the resulting charge's payment_method_details reflects the correct cnp_type or equivalent indicator
Known gotchas
Misuse of the MOTO flag on online transactions can constitute fraud misrepresentation to the card network and shift liability incorrectly; only use it for genuine MOTO scenarios
MOTO requires your business to be registered for MOTO acceptance with your acquirer; using the MOTO indicator without proper MCC and merchant category registration can cause declines or compliance issues
Because MOTO bypasses SCA, the merchant bears greater fraud liability for MOTO transactions in SCA-covered regions; ensure your fraud controls are proportionally stronger for the MOTO channel
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp