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
| Your layer | The package | Key it holds |
|---|---|---|
| A browser page | @wajub/js, or @wajub/react, /vue, /svelte | A session token |
| Your backend | One of seven server SDKs | Your sk. secret key |
| A mobile app | wajub_mobile, @wajub/react-native, com.wajub:wajub-mobile-compose | A session token |
| A terminal or CI job | @wajub/cli | A restricted rk. key |
| A WordPress site | The Wajub plugin | Configured in the admin |
Most integrations use two of them: a server SDK to create the payment, and a browser or mobile package to collect it.
One rule governs the whole list
A secret key never leaves your server. The browser and the mobile app get a session token,
scoped to one payment, which cannot list, refund or read anything else. The API blocks any
sk. request arriving with a browser origin and emails the key owner.
The server SDKs
Seven packages, the same eighteen resources, the same method names transposed into each language.
| Language | Package | Registry |
|---|---|---|
| Node.js | @wajub/node | npm |
| Python | wajub | PyPI |
| PHP | wajub/wajub-php | Packagist |
| Go | github.com/wajubhq/wajub-go | Go modules |
| Ruby | wajub | RubyGems |
| Java | com.wajub:wajub-java | Maven Central |
| C# | Wajub | NuGet |
Versions, runtime floors and the constraints that eliminate an option are on SDKs & Libraries and Choose your SDK.
Start here
Related pages
- SDK QuickstartA key, an install line, and one working call.
- Choose your SDKThree questions, one package.
- 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.