Engineering kickoff ยท Payments team

Paylane to Stripe by the end of Q2

We are moving card payments to Stripe. Approved October 21, with 2 engineers for Q1 and Q2. Today we agree what is fixed and what the team still has to design: token migration, the parallel run and the cutover.

We are leaving Paylane because it costs more and goes down

Card fees on last year's volume: Paylane $412k, Stripe at its quoted rate $298kPaylane: $412kStripe quote: $298k

Fees on last year's volume. Stripe would have saved $114k.

Outages
3 in the last 6 months, 9 hours in total, about $60k in lost checkouts (finance estimate).
Not chosen
Staying and renegotiating (Paylane offered 8% off), or moving to Adyen, a 6-month integration.

The provider, deadline and budget are fixed

Provider
Stripe, for all card payments now on Paylane.
Deadline
End of Q2.
People
2 engineers for Q1 and Q2.
Budget
A $25k migration fee.
Not yet designed
How we run both providers in parallel, and how we cut over.

Saved card tokens depend on Paylane, and Paylane has given no date

Saved card tokens move from Paylane through Stripe's migration service to Stripe; there is no direct exportPaylanesaved card tokensStripe'smigration serviceStripeNo direct exportfrom Paylane.Needs Paylane's cooperation:Paylane said yes, but gave no date.

The parallel run and cutover are ours to design, around renewals in flight

Renewals
Subscription renewals will still be in flight while we switch.
Saved cards
They move only once Paylane does its part of the token migration.
Deadline
All card payments are on Stripe by the end of Q2.

These four questions shape how we build the migration

Token migration
When will Paylane do its part for Stripe's migration service? Saved cards can't move until then.
Parallel run
How do Paylane and Stripe run side by side? It is not designed yet.
Cutover
How do we switch with subscription renewals in flight?
Old webhook handler
Can we drop it? The tech lead asked, and nobody has answered yet.