Feature

Offer payment processing. Through the same API.

Offer your merchants payment processing through the API you already use, and earn on every payment they take.

The Orchestra API with an optional path to processing
The Orchestra API with an optional path to processing

One integration. Two ways to process.

Connect a merchant’s existing provider account, or onboard the merchant to Orchestra’s processing. Either way you earn: mark up the connectivity, and with Orchestra’s processing also take a share of the processing revenue.

The same API request goes to the merchant’s provider or to supported processing, where available
The same API request goes to the merchant’s provider or to supported processing, where available

Work with the full payment lifecycle.

Charge immediately, or pre-authorize and capture later. Refund captured payments or void uncaptured authorizations.

Charge then refund; or pre-auth, capture, refund; or pre-auth then void
Charge then refund; or pre-auth, capture, refund; or pre-auth then void
A processor result passes through Orchestra and becomes a standard payment result
A processor result passes through Orchestra and becomes a standard payment result

Keep response handling consistent.

Orchestra returns payment results in its standard response format, regardless of the configured processing path.

Processing in eight markets.

Orchestra onboards the merchant to a white-label processor for cards, Apple Pay and Google Pay, so you don’t negotiate a separate processing agreement. Bank payments are also onboarded through Orchestra, in the US, the EU, the UK and Israel.

Card processing available in

  • United States
  • United Kingdom
  • European Economic Area
  • Hong Kong
  • Malaysia
  • Thailand
  • Philippines
  • Turkey

Build it

Authorize now. Capture when ready.

The same calls cover the whole lifecycle: charge, authorize, capture, void and refund, with one response format.

const response = await fetch('https://api.orchestrasolutions.com/PaymentGateway/authorize', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-Api-Key': 'YOUR_API_KEY'
  },
  body: JSON.stringify({
    amount: 50.00,
    currency: 'USD',
    paymentGatewayAccountName: 'stripeProduction',
    card: {
      cardNumber: '@nQGywsQE9gbURtrXEjTZwtWqeMdK9nsO',
      cardHolderName: 'Jane Smith',
      expirationMonth: 12,
      expirationYear: 2027
    }
  })
});

const result = await response.json();
// Save the transaction ID for capture/void/refund

Authorize $50 and keep the transaction ID for capture. From the docs.

Go deeper on payment processing

  • Person using card to make payment

    Payment Orchestration vs. Payment Processing: Understanding the Differences for Modern Businesses

    Payment processing handles transactions. Payment orchestration decides how, where, and through whom they run. Learn how the two layers differ.

     
  • Understanding And Optimizing Subscription Payment Services

    Payment Processor vs Payment Gateway: Key Differences

    Payment processors and payment gateways handle different parts of every card transaction. Here’s how to tell them apart, how they work together,…

     
  • Payment Authorization vs Settlement: How They Differ

    Authorization approves a transaction in seconds. Settlement moves the money in days. Learn how both stages work, where payments fail between them,…

     

More from the same API.

Related on this site

Test payment processing in the sandbox.

100 live requests every month, plus unlimited sandbox testing. No credit card required.

Sandbox unlimited testing | Live 100 requests / month