Orchestrapay for WooCommerce

Description

Orchestrapay for WooCommerce adds Orchestrapay as a payment method in your store. When a customer places an order, the plugin creates an Orchestrapay payment intent on your server and redirects the customer to the Orchestrapay hosted payment page to pay. Orchestrapay then returns the customer to your store’s order-received page.

Payment is confirmed server-side by an Orchestrapay webhook (with a thank-you-page status check as a fallback), then the WooCommerce order is marked paid.

Features

• Works on both the classic checkout and the WooCommerce Checkout block.
• One “Pay Online” option; the Orchestrapay page presents every method configured on your Orchestrapay Payment Form (cards, wallets, and more).
• Choose which Orchestrapay Payment Form to show, loaded directly from your account.
• Server-side confirmation via webhook, with a fallback so it also works on sites a webhook cannot reach.
• Refunds from the WooCommerce order screen.
• API keys are validated when you save them.

Requirements

• An Orchestrapay account and API keys (publishable orch_pk_... and secret orch_sk_...). Get them at https://www.orchestrapay.com/dashboard/api-keys
• WooCommerce 7.0 or newer.

External services

This plugin connects to Orchestrapay, a third-party payment orchestration service, to process payments. This connection is required for the plugin to function and is used only when you have configured the gateway with your Orchestrapay API keys.

What is sent, when, and to where:

• Creating a payment (server to Orchestrapay API). When a customer places an order with this payment method, your server sends the order amount, currency, and the customer’s name, email, and phone number (as entered at checkout), plus order metadata, to the Orchestrapay API to create a payment intent. The API host is derived from your key’s region: https://api-us1.orchestrapay.com, https://api-eu1.orchestrapay.com, or https://api-eg1.orchestrapay.com. The same API is used to retrieve payment status, issue refunds, and list your Payment Forms.
• Paying (customer’s browser to Orchestrapay). After placing the order, the customer is redirected to the Orchestrapay hosted payment page at https://pay.orchestrapay.com/pay/{payment_intent} to enter their payment details and pay. Card and payment details are entered on Orchestrapay’s page and are never handled by your site. Orchestrapay then returns the customer to your store.
• Webhooks (Orchestrapay to your site). Orchestrapay sends payment status notifications to your site’s REST endpoint to confirm orders.

Your Orchestrapay secret key is stored in your site’s database and is only ever used server-side; it is never exposed to the browser. Only your publishable key and the payment intent id are sent to the browser.

Orchestrapay’s terms and privacy policy:

• Terms of Service: https://www.orchestrapay.com/legal/terms
• Privacy Policy: https://www.orchestrapay.com/legal/privacy

Technical details