Title: Orchestrapay for WooCommerce Author: orchestrapay Published: Ọwẹ́wẹ̀ 24, 2026 Last modified: Ọwẹ́wẹ̀ 24, 2026 --- Ṣàwárí àwọn plugin ![](https://s.w.org/plugins/geopattern-icon/orchestrapay.svg) # Orchestrapay for WooCommerce Láti ọwọ́ [orchestrapay](https://profiles.wordpress.org/orchestrapay/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/orchestrapay.1.0.1.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/orchestrapay/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/orchestrapay/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/orchestrapay/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/orchestrapay/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/orchestrapay/) ## Àpèjúwe 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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá:’ 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Ìtumọ̀ Yorùbá: ’s REST endpoint to confirm orders. Your Orchestrapay secret key is stored in your siteÌtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’s terms and privacy policy: * Terms of Service: https://www.orchestrapay.com/legal/terms * Privacy Policy: https://www.orchestrapay.com/legal/privacy ## Ìgbéwọlẹ̀ 1. Upload the plugin to `wp-content/plugins/orchestrapay`, or install it from the Plugins screen. 2. Activate the plugin. 3. Go to WooCommerce > Settings > Payments > Orchestrapay. 4. Enter your Orchestrapay publishable and secret keys, optionally pick a Payment Form, and enable the method. ## FAQ ### Do I need an Orchestrapay account? Yes. The plugin is an interface to the Orchestrapay service; you need an account and API keys. ### Where do customers enter their card details? On OrchestrapayÌtumọ̀ Yorùbá: ’s secure hosted payment page, which they are redirected to after placing the order. Card data never touches your server. ### Does it work with the block checkout? Yes. The method appears on both the classic checkout and the WooCommerce Checkout block. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “Orchestrapay for WooCommerce” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ orchestrapay ](https://profiles.wordpress.org/orchestrapay/) [Túmọ̀ “Orchestrapay for WooCommerce” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/orchestrapay) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/orchestrapay/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/orchestrapay/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/orchestrapay/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/orchestrapay/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 1.0.1 * Fix: a fresh payment is now started on every click of the pay button. Returning to a checkout after leaving the payment page (for example when the previous payment had timed out) no longer sends the buyer back to an expired payment page. * Fix: changing the cart after opening the payment page now charges the updated total instead of the original amount. * Fix: using the “back” arrow on the payment page (leaving without paying) now returns the buyer to the payment step to finish, instead of an order-received page that looked like a confirmation. Unpaid orders no longer show a “thank you” confirmation message. * The previous, still-open payment is canceled when a new one is started, so a buyer cannot be charged twice. #### 1.0.0 * Initial release. ## Àkójọpọ̀ Meta * Ẹ̀yà **1.0.1** * Ìgbàgbọ́hùn tó kẹ́yìn **ọjọ́ 3 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.1.2** * Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/orchestrapay/) * Àwọn àmì * [checkout](https://yor.wordpress.org/plugins/tags/checkout/)[credit card](https://yor.wordpress.org/plugins/tags/credit-card/) [payment gateway](https://yor.wordpress.org/plugins/tags/payment-gateway/)[payments](https://yor.wordpress.org/plugins/tags/payments/) [woocommerce](https://yor.wordpress.org/plugins/tags/woocommerce/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/orchestrapay/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/orchestrapay/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/orchestrapay/reviews/) ## Àwọn Olùkópa * [ orchestrapay ](https://profiles.wordpress.org/orchestrapay/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/orchestrapay/)