Connect to Payment Links accounts
Shuttle Payment Links is Shuttle’s own app for merchants: a merchant signs up, connects their payment processor and sets up their branding, then sends payment links and takes payments. If your merchants have, or can open, a Payment Links account, your platform can connect to it and work through it, instead of building payments into your product. This is sometimes called Payment Links for Platforms.
It uses account sharing. Shuttle Payment Links is the owner of the merchants’ accounts; your platform is the third party. Shuttle gives you an OAuth client, each merchant connects their account to your platform once, and you then create payment links and take payments in their account, and hear about them by webhook.
If you would rather create the merchants’ accounts yourself and keep payments inside your own product, see Choosing an approach.
Two ways to build it
Section titled “Two ways to build it”- With no code. Use Zapier, Make or Cyclr to create a payment link when something happens in your platform, and update your platform when it is paid. See No code: Zapier, Make and Cyclr.
- Against the API. Your platform connects each merchant through OAuth, creates links with the Payment Links accounts API, and listens for payments with webhooks. See Connecting merchants and Actions and events.
This section is written for multi-tenant workflow applications, integration platforms (iPaaS), AI agents and SaaS platforms creating payment links for many merchants.
Certification
Section titled “Certification”Integrations against the API are certified by Shuttle before they go live, and the live client ID and client secret are only issued once yours is certified. To be certified, you must:
- Follow the implementation in Actions and events exactly, including its field names and ordering, unless Shuttle agrees otherwise
- Cover all the Payment Links functionality it requires
- Meet the further requirements Shuttle gives you during certification
Before you start
Section titled “Before you start”- Your platform can run an OAuth 2.0 client flow, and store credentials and tokens for many merchants securely
- You can ask each merchant whether to connect sandbox or live
- Contact Shuttle support for your sandbox client ID and client secret
Was this page helpful?
What went wrong?
Thanks for telling us.