> ## Documentation Index
> Fetch the complete documentation index at: https://developers.orchestrasolutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payments Library vs REST API

> Compare Orchestra integration options: JavaScript library with built-in UI vs direct REST API calls.

Orchestra offers two integration approaches. Both provide automatic gateway failover and access to {supportedIntegrations} payment providers.

## 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

[Get started with Library →](/quickstart)

## 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 →](/quickstart)

## 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

<CardGroup cols={2}>
  <Card title="Library Setup" icon="browser" href="/guides/library/setup">
    Full Payments Library integration
  </Card>

  <Card title="Charge Payments (REST)" icon="code" href="/guides/rest-api/charge">
    REST API charge implementation
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Get started in 5 minutes
  </Card>

  <Card title="Complete Example" icon="github" href="/guides/library/complete-example">
    Full working code sample
  </Card>
</CardGroup>