Libraries
The three families of Wajub packages, and which one your layer needs.
Every Wajub package wraps the same HTTP API. What separates them is where the code runs, and that is the only question you need to answer to pick one.
Related pages
Where your code runs
That question decides the package. The table that answers it, from the browser to the command line, and the rule that governs it, the secret key never leaving your server, are on SDKs. Most integrations use two packages: a server SDK to create the payment, and a browser or mobile package to collect it.
Start here
Related pages
- SDK QuickstartA key, an install line, and one working call.
- Choose your SDKRuntime floors and the constraints that rule one out.
- Integration pathsRedirect, embed or your own form. Which and why.
- Sessions & securityWhich key goes where, and what each one may do.
- Mobile SDKsA native payment sheet, without a WebView.
- Example projectsWorking code, and where each piece lives.