Skip to main content
This page is part of the REST API Guides. Using the JavaScript library instead? See Payments Library Guides.
Some payment gateways require additional parameters or have unique configuration requirements. This page documents gateway-specific details you may need when integrating.
These requirements apply when using the REST API directly. The Payments Library handles most of these automatically.

Adyen

The ShopperInteraction parameter specifies the sales channel and whether the customer is returning.
For POS accounts, set ShopperInteraction to "Ecommerce".

AMEX

The myRef parameter is required and must contain 6 or more characters.

Authorize.net

The ECCenabled parameter controls refund behavior:

Cardstream

Cardstream uses the OrderDesc parameter to provide additional order description.

Caterpay

Caterpay uses the OrderDesc parameter to provide additional order description.

Credorax

Credorax requires integration certification. Orchestra’s integration is certified with Credorax. Contact support@orchestrasolutions.com if you need certification documentation.

Elavon

Include the RebatePWD (rebate password) in your credentials:

First Data (FirstDataIPG)

First Data requires:
  1. Client certificate authentication - Upload your certificate through the Orchestra Portal
  2. Client IP address - Provide in the PayerDetails object

Gateline

Gateline has the same requirements as First Data:
  1. Client certificate authentication - Upload via portal
  2. Client IP address - Required in PayerDetails

Global Payments WebPay

The myRef parameter must be a 15-digit numeric value.

Heartland

Heartland has two requirements:
  1. myRef must be numeric only (no letters or special characters)
  2. Integration certification required - Orchestra’s integration is certified

Kortapay

Void and Refund operations on Kortapay need the original transaction amount. This is configured with Orchestra rather than passed as a request field.

Contact Support

Email support@orchestrasolutions.com to set up Kortapay Void/Refund requirements for your account.

PayGate

Your PayGate merchant account must have the “auto-settle” flag set to “off”. Configure this in your PayGate merchant dashboard before integrating.

Pesopay

Pesopay has two requirements:
  1. myRef must be unique on every submission
  2. Void operations must use the GatewayReference from the PreAuth response, not Capture

Stripe (PaymentIntent)

3D Secure Support

To enable 3DS transactions, contact Stripe and request enabling the payment_method_options.card.request_three_d_secure option on your account.

Subscriptions

Use the SetupFutureUsage parameter to enable Stripe Subscriptions:

Wirecard

Wirecard uses the OrderDesc parameter to provide additional order description.

Worldpay

Worldpay has two requirements:
  1. IsDigital parameter - Required, defaults to true
  2. Integration certification required - Orchestra’s integration is certified

Zeamster

Zeamster uses the OrderDesc parameter to provide additional order description.

Zoop

Zoop supports splitting payments into installments (micro credit). This is configured with Orchestra rather than passed as a request field.

Contact Support

Email support@orchestrasolutions.com to set up Zoop installment support for your account.

Payment Operations

Full endpoint documentation

Payment Gateway Accounts

Configure gateway credentials