EMV Secure Remote Commerce (SRC) defines a standardized checkout experience where cardholders store cards with SRC systems (run by Visa, Mastercard, Amex, Discover) and check out without re-entering card details
As a merchant, you integrate with an SRC Initiator (SRCi) — either a network-provided SDK or a third-party solution — which handles the UI widget, cardholder recognition, and card selection
The SRCi communicates with the SRC systems on behalf of the cardholder using the cardholder's email as an identifier to recognize them across devices and networks
Upon checkout completion, the SRCi returns a checkout response payload containing a checkout payment token or a DPAN with cryptogram that you pass to your payment processor for authorization
Merchant integration typically involves adding the SRCi JavaScript SDK to your checkout page, initializing it with your merchant profile data, and implementing callbacks for the checkout completion event
Test in sandbox environments provided by the individual networks (Visa, Mastercard) before enabling production Click to Pay to ensure the checkout payload is correctly handled by your processor
Known gotchas
Each card network operates its own SRC system; a unified checkout experience requires the SRCi to query all participating networks and present the cardholder's cards from each
The Click to Pay button must meet EMV SRC brand guidelines; using a non-compliant button may violate network acceptance agreements
Not all payment processors accept the SRC checkout token directly; verify your acquirer's support for DSRP or the specific token format returned by the SRCi before going live
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