First, we understand your platform. Then we build the offer with you.
Your product, your customers and how they take payments today come first. We work out what to build, how to price it, what stays open and how to explain it to customers. Then we launch it with you, get customers using it and improve it after launch.
From understanding the product to getting it used
Each stage gives your team something to act on. Choose a stage to see what happens, what you leave with and where the detail is.
Stage 1 of 5
Understand your platform
We start with your product and your customers. How do they take payments today? What matters to them? Where are customers dropping out, or payments failing?
What you leave with
- Your product and customer groups
- How customers take payments today
- What needs attention first
Thirty minutes with a payments engineer. Bring your volume and how your customers pay today.
Decide what stays open
Which features should every customer keep? Which would give them a reason to use your payments? We work through that with you. The choice needs to make sense for customers and for your business.
For each feature, we write down who can use it, what they pay and how you will explain it. That gives your product, sales and support teams the same answer.
Choose how much we run with you
The proposal sets out what your team does, what we take on and what it costs.
Guide
We work out the offer, pricing, feature choices and launch plan with you. Your team runs it, with us there to guide and review.
Run
We also run the customer communications and follow-up we have agreed. It goes out in your brand, with your sign-off, and we help customers get started.
Run and build
We also build the payment products we have agreed with you. Your developer connects them to your software. We make sure both teams know who is doing what.
What your team brings
You know your product and customers. We bring payments experience, pricing and go-to-market work, and the people to help customers adopt. We make the decisions together and agree where your approval is needed.
- Help us understand your product and customers
- Share the relevant data on agreed terms
- Sign off pricing, feature access and messages
- Build your software integration
Payment infrastructure and support
Our regulated acquiring partner provides the payment infrastructure and holds the funds. You work with Synapto on the product, pricing, go-to-market, adoption and payment support.
Your developer connects your software. Before work starts, you have in writing what we build, who helps customers get started and how your team reaches us for payment support.
- Infrastructure and funds with our regulated acquiring partner
- Product and go-to-market work with Synapto
- Your developer connects your software
- Payment questions and support through Synapto
Start at stage one
The payments review is where stage one starts. You can also start from the numbers, or give your developer the documentation first.
- Book a payments reviewThirty minutes with a payments engineer on your volume and customers
- See what you could earnSix questions, and a rounded range from your own figures
- Read the documentationFor your developer: quickstart, API reference and webhooks
- Ask us a questionSend it to the team, and we reply by email
What platforms ask about the process
We start by working out what will work for your platform: the product, offer, pricing and go-to-market. Then we stay involved in the work we have agreed, whether that is building payment products, running customer communications, helping customers get started or reviewing payment problems.
No. Nothing is forced. New customers start on your payments by default, and existing ones move when there is a good reason and a good moment for them, such as a renewal or a new site.
Mandates can usually be moved rather than re-signed by every customer. It is not automatic and it is not instant, so it gets planned rather than promised, and we will tell you what your setup allows before anyone moves.
We build the payment products with you. Your developer owns your own product's integration, with a payments engineer here answering the payments questions while they build. We never put a date on your team's work.
The review is where stage one starts
Thirty minutes on your product, your customers and how they pay today. If there is a fit, discovery follows, and you get the first written output at the end of it.
