Quick Comparison
| Capability | Payments Library | REST API |
|---|---|---|
| Integration method | npm package | Direct HTTP calls |
| Card collection | We handle it | You handle it |
| PCI compliance | Out of scope | Your responsibility |
| UI control | Pre-built components | Full customization |
| 3D Secure | Built-in | Manual implementation |
| Digital wallets | Native support | API integration required |
| Deployment speed | Rapid | Custom development |
Choose Library if you:
- Want the fastest path to accepting payments
- Prefer to stay out of PCI scope
- Need Google Pay, Apple Pay, or bank transfers quickly
- Want battle-tested payment UX
- Don’t want to build payment UI from scratch
Choose REST API if you:
- Have existing payment flows you want to enhance
- Need pixel-perfect UI control
- Already handle PCI compliance
- Use third-party tokenization providers
- Prefer backend-only integration
Can I use both?
Yes. Many implementations use the Library for customer-facing payments and the REST API for backend operations like refunds, reporting, or recurring billing.Related Guides
Library Setup
Full Payments Library integration
Charge Payments (REST)
REST API charge implementation
Quickstart
Get started in 5 minutes
Complete Example
Full working code sample