What are you trying to do?
This is the documentation for building with Wasp. Everything below is organised by the job you are doing, not by how these pages happen to be filed — so you should not need to learn our structure before you can find your answer.
Everything linked from this page is open to you right now, with no account.
If you are still deciding whether Wasp fits, the Wasp home page explains what the platform gives you. If you already know you are building and want the implementation guides, the API reference and a sandbox to test against, start with Register, and get access to build — it sets out what you get at each step and who grants what.
Start here
New to Wasp. Enough to understand what it does and decide how you will use it.
- Understand what Wasp is
The platform, the three parts of a payment, and where your own code sits in one.
- Decide how much Wasp should own
The first decision, and the one everything else follows from. Four ways to take a payment, and what each asks you to build.
- See where Wasp Checkout fits
How Wasp sits alongside the shop, cart and order system you already have.
- See what Google Pay and Apple Pay need from you
What each wallet needs from you, from Google and from Apple, in each checkout: to test, and to go live.
- Look up a term you have just met
Plain-language definitions, so no page assumes payments knowledge you have not been given.
Get set up
What you need before you can build, and how to get it.
- Register, and get access to build
Registering takes a minute and proves who you are. The implementation guides, the API reference and the ability to take a payment are granted separately — this explains exactly how, and who grants them.
- See what the API references cover
The two API references, what each one covers, and how you get access to each.
Know the boundaries
What Wasp keeps away from you, and what stays your responsibility.
- Handle credentials and secrets safely
What belongs on your server, what may reach a browser, and what must never be logged.
- See what this portal shows whom
Who can read what here, what registering changes, and what it does not.
What you will not find here
This portal documents the interfaces you integrate against and the boundaries around them. It does not publish API signing secrets, merchant credentials, raw wallet tokens, decrypted card data, card security codes (CVV/CCV), cryptograms, wallet private keys, acquirer credentials, internal routing or risk rules, or any other merchant's data.
If you cannot find something you expected, Support is the right next stop.