Skip to main content
Orchestra offers two integration approaches. Both provide automatic gateway failover and access to payment providers.

Quick Comparison

CapabilityPayments LibraryREST API
Integration methodnpm packageDirect HTTP calls
Card collectionWe handle itYou handle it
PCI complianceOut of scopeYour responsibility
UI controlPre-built componentsFull customization
3D SecureBuilt-inManual implementation
Digital walletsNative supportAPI integration required
Deployment speedRapidCustom 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
Get started with Library →

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
Get started with REST API →

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.