Go-to-market for a payment product: certification, pilot and launch

Going to market with a payment product is a regulated process, not a marketing event. Before the first customer payment can be processed, the product must be certified by the scheme, the correspondent banks must be onboarded, the screening must be configured, the reconciliation must be tested, and the operations team must be trained. A launch date that is set before these are done will slip, and a launch that happens before they are done will fail in production. The go-to-market plan must therefore be built backwards from the certification date, not forwards from the marketing date. Certification is the gate. For a SEPA product the firm must be admitted to the scheme, must pass the certification test pack, and must prove it can send and receive the scheme messages correctly. For a card product the firm must be certified by the scheme for authorisation, clearing and settlement, and must pass the scheme's security assessment. For a SWIFT product the firm must have a BIC, must be connected to the SWIFT network, and must have passed the customer security programme attestation. Each certification has a window, a test pack, and a failure rate, and the plan must allow for a failed attempt. The pilot is the controlled exposure. A payment pilot runs with a small number of customers, a limited volume, and a defined set of corridors, and every payment is monitored. The pilot has entry criteria, which state what must be true before it starts, and exit criteria, which state what must be true before it can expand. The exit criteria must include the straight-through processing rate, the exception rate, the average processing time, and the number of open defects. A pilot that expands before its exit criteria are met is not a pilot, it is a launch without a safety net. Launch communication in payments must be precise. Customers need to know which corridors are live, what the cut-off times are, what the fees are, and what the status information will look like. Correspondent banks need to know the expected volumes, the message formats, and the contact for exceptions. The operations team needs to know the runbook, the escalation path, and the rollback plan. A launch where the customers know more than the operations team is a launch that will generate support calls the operations team cannot answer. The rollback plan is the part of the launch that is most often omitted. If the new product fails in production, the firm must be able to return to the old product, or to stop taking new payments, without losing the payments that are already in flight. The rollback plan must state the trigger, the decision maker, the steps, and the reconciliation that proves no payment was lost or duplicated. The plan must be tested before launch, because a rollback plan that has never been tested is a hope, not a plan. Post-launch monitoring is a product activity, not an operations activity. The product owner must watch the straight-through processing rate, the exception rate, the customer complaints, and the revenue per payment, and must be ready to change the product in the first weeks. The first month of a payment product always reveals problems that testing did not find, because real customers use the product in ways the testers did not imagine. The requirements must state the monitoring dashboard, the alert thresholds, and the weekly review. For a business analyst, the go-to-market plan is a checklist with owners and dates. The checklist must include certification, correspondent onboarding, screening configuration, reconciliation testing, operations training, pilot entry and exit criteria, launch communication, rollback plan, and post-launch monitoring. The acceptance criteria must include a test where the launch is rehearsed end to end, including a failure and a rollback. Last reviewed 7 November 2026. Further reading: the EPC SEPA adherence and certification process; the SWIFT Customer Security Programme; the Visa and Mastercard certification guides; the Bank of England guidance on payment system go-live.