Gateway SDK & Developer Experience

Challenge

Every day between a merchant signing and that merchant processing their first live transaction is a day of revenue neither party earns. Time-to-live was long, and the delay was not in approvals — it was in integration.

Merchants hit the same obstacles repeatedly: sandbox credentials that behaved differently from production, documentation that explained parameters but not sequences, error responses that reported that something failed without saying what to do about it, and a certification step that surfaced problems only after the integration was already built.

Each obstacle individually looked minor. Together they turned a nominally straightforward integration into weeks of back-and-forth with support.

Approach

Instrument the funnel merchants actually walk. We could see when merchants signed and when they went live, but almost nothing in between. Instrumenting each integration stage showed where merchants stalled — and the stalls clustered in places the team had assumed were easy.

Read the support queue as a design document. Recurring support tickets are a precise map of where a product misleads people. The most common tickets pointed directly at the highest-value fixes.

Optimize for first successful call, not for API surface. The metric that predicts a successful integration is how quickly a developer gets one call to work. Everything else follows from that first success.

Make errors instructive. An error that names the problem and the next action removes an entire support round trip.

Move certification earlier. Validating continuously during integration, rather than as a terminal gate, meant problems surfaced when they were still cheap to fix.

Solution

1. Redesigned SDK with sensible defaults, so the common integration path required minimal configuration.
2. Sequence-oriented documentation organized around end-to-end flows rather than endpoint reference.
3. Actionable error responses naming both cause and remedy.
4. Sandbox-production parity so behavior verified in test held in production.
5. Continuous certification replacing the terminal gate.

Results

• Merchant time-to-live fell 40%. Merchants started processing — and earning — substantially sooner.
• Support load shifted from repetitive integration questions toward genuinely novel ones.

What I'd carry forward

The instinct with a slow onboarding funnel is to add help: more documentation, more support, more hand-holding. Most of the 40% came from the opposite move — removing the decisions merchants had to make before their first successful call. Every required parameter with no sensible default is a place an integration can stall.

Sandbox-production parity deserves specific mention. Divergence there does not just cost time, it costs trust: a merchant who gets burned once by test behavior that did not hold in production re-verifies everything from then on.