WordPress plugin intelligence profile

Fabrick Payment Orchestra

Accept card and alternative payments via Fabrick Payment Orchestra for WooCommerce: secure WebComponent checkout, tokenization, subscriptions.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.2
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.4 · PHP 8.0
Directory statusactive
Last directory update29 Oct 20264d ago
Active installations10Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Fabrick Payment Orchestra version 1.0.2 as active, updated 4d ago and tested up to WordPress 7.1.

Overview

About this plugin

Fabrick offers solutions to meet and anticipate all needs in the field of payment acceptance, on all physical and digital channels. The offer consists of a single platform to accept payments through physical and digital gateways such as POS, Ecommerce solutions, Banking-as-a-Service (BaaS) and omnichannel solutions in continuous evolution to meet market changes.

With Fabrick Payment Orchestra, you can:

  • Accept payments from all major credit cards
  • Accept payments from different alternative payments like PayPal, Apple Pay, Google Pay and many others – and manage them from the same dashboard
  • Be compliant with PCI-DSS specifications, so that you don’t need to store your customers’ credit card numbers
  • Count on 3DS2.X support

WooCommerce Blocks Compatibility

The plugin is fully compatible with WooCommerce Blocks checkout. All payment methods are supported in both classic checkout and blocks checkout modes. There is no need to disable WooCommerce Blocks checkout.

Requirements

  • WooCommerce 9.0 or newer, WordPress 6.4 or newer, and PHP 8.0 or newer
  • Fabrick account with Payment Orchestra, Web Components, and REST APIs enabled
  • Credentials: Shop Login and API Key (sandbox or production)
  • HTTPS on the store domain (recommended / required in production)
  • For Apple Pay / Google Pay: domain prerequisites and activation on the Fabrick side (see the official documentation)

Available Payment Methods

Available payment methods depend on the services activated on your Fabrick account.

  • Alipay
  • Amazon Pay
  • Apple Pay
  • AppPago
  • BANCOMAT Pay
  • Bancontact
  • EPS
  • Fabrick Pay by Bank
  • Google Pay
  • Klarna
  • Konbini
  • Multibanco
  • MyBank
  • iDEAL
  • PayPal
  • Paysafecard
  • Przelewy24
  • Satispay
  • UnionPay
  • WeChat Pay

Benefits

  • Accept credit card payments directly on your store
  • Accept payments with a variety of alternative methods to increase conversion by allowing customers to pay in their own preferred way
  • Reduce fraud risk with Fabrick’s risk-based 3-D Secure authentication (RBA)

Security

  • No credit card data is saved on your servers during the payment process
  • All major credit card brands are supported (Visa, Mastercard, American Express)
  • 3DS2.X support

Support

com.

org account netingweb).

The complete plugin installation guide is available in the Fabrick documentation.

External services

) to process payments. This connection is required for the core functionality of the plugin: without it, no payment can be created, verified, or refunded.

1. Orchestra REST API

  • Endpoints: https://sandbox.gestpay.net (sandbox) and https://ecomms2s.sella.it (live).
  • What it is used for: creating payment sessions, verifying payment outcomes ( payment/detail ), processing refunds and cancellations, retrieving the payment methods enabled on your terminal, and deleting saved-card tokens.
  • When data is sent: when a payment is created or verified, a refund or cancellation is sent, the method list is refreshed, a saved card is deleted, or the merchant runs a connection test.
  • What data is sent: your shop login and API key (authentication); order amount and currency; a shop transaction reference; callback URLs; the payment language code; WooCommerce, plugin, and WordPress versions. For 3-D Secure the request also includes the buyer name, email, and billing and shipping address. For some alternative methods, such as Klarna, it also includes order lines. When tokenization or subscriptions are enabled, it includes payment token references and recurring transaction identifiers. Full card numbers (PAN) and CVV never pass through or reach your server.

2. Orchestra checkout WebComponent

  • Endpoints: https://sandbox-web.axerve.com (sandbox) and https://web.axerve.com (live).
  • What it is used for: the fbk-elements.js script is loaded in the customer’s browser when they open the order pay page and renders the <fbk-checkout> payment form (cards and alternative payment methods). The customer enters the card number and the security code in that component; those values are transmitted to Fabrick only.
  • Why it is loaded externally: card data is entered directly into the Fabrick-hosted component and is transmitted to Fabrick only, keeping your server out of PCI scope (SAQ-A). Loading this script from Fabrick’s servers is a requirement of the payment service and cannot be bundled with the plugin.

3. Apple Pay domain association (optional)

well-known/. This is only relevant if you activate Apple Pay on your terminal.

Service provider

, Piazza Gaudenzio Sella 1, 13900 Biella, Italy.

  • Privacy policy (payment service users): fabrick.com/en-gb/privacy/privacy-policy-payment-services/
  • Privacy policy hub: fabrick.com/en-gb/privacy/
  • Service documentation: docs.fabrick.com

A. as payment service provider.

Actions and filters

Developer hooks use the fabrick_orch_* prefix and are a stable public API (additive changes only). Register them from a custom plugin with add_action() / add_filter().

Rules of thumb

  • Prefer fabrick_orch_payment_completed / _failed / _pending for business logic — they run after verified payment/detail.
  • fabrick_orch_callback_received is raw ingress (not yet verified); do not treat it as “paid”.
  • Filters must keep the expected return type ( array, string, bool, …). Do not strip required Orchestra fields ( shopLogin, responseURLs, amounts, binding IDs).
  • Hooks must not bypass nonces, capabilities, token ownership (anti-IDOR), or payment/detail verification.
  • Legacy GestPay aliases receive REST-oriented data (arrays), not SOAP SimpleXMLElement.

Example — note on verified payment

add_action( 'fabrick_orch_payment_completed', function( $order, $payment_detail, $source ) { $order->add_order_note( 'Fabrick payment verified ('. $source. ' ); }, 10, 3 );

Example — filter create payload

add_filter( 'fabrick_orch_create_payment_request', function( $payload, $order, $context ) { /* enrich $payload; return array */ return $payload; }, 10, 3 );

Example — ecommerce EC transDetails (one-shot)

add_filter( 'fabrick_orch_ecommerce_trans_details', function( $details, $order ) { return $details; }, 10, 2 );

Actions — payment lifecycle (callback)

  • fabrick_orch_callback_received( string $source, array $params, WC_Order|null $order ) — callback received (buyer or S2S); not yet verified.
  • fabrick_orch_before_callback_processing( WC_Order $order, string $source, array $params ) — before payment/detail drives order status.
  • fabrick_orch_after_callback_processing( WC_Order $order, string $source, array $payment_detail ) — after callback processing completes.
  • fabrick_orch_payment_completed( WC_Order $order, array $payment_detail, string $source ) — payment confirmed completed.
  • fabrick_orch_payment_failed( WC_Order $order, array $payment_detail, string $source ) — payment failed.
  • fabrick_orch_payment_pending( WC_Order $order, array $payment_detail, string $source ) — payment pending (e.g. async APM).

-

fabrick_orch_process_payment_error( Throwable $error, WC_Order|null $order, array $context ) — checkout, callback, or Pay By Link error.

$source is one of: s2s, buyer_ok, buyer_ko, recovery, admin, checkout, subscription, legacy.

Actions — checkout, admin, refunds, tokens, subscriptions, Pay By Link

  • fabrick_orch_payment_fields( string $gateway_id ) — before payment fields / WebComponent render on the pay page.
  • fabrick_orch_gateway_settings_before_cards( object $gateway ) — gateway settings screen extension point.
  • fabrick_orch_connection_test_result( bool $success, array $result, array $context ) — after AJAX connection test.
  • fabrick_orch_shop_login_changed( string $environment, string $shop_login, string $previous ) — shop login credential changed.
  • fabrick_orch_before_refund( WC_Order $order, float|null $amount, array $context ) — before refund API call.
  • fabrick_orch_refund_success( WC_Order $order, array $response, float|null $amount ) — refund succeeded.
  • fabrick_orch_refund_failed( WC_Order $order, array $response, Throwable|null $error ) — refund failed.
  • fabrick_orch_before_cancel( WC_Order $order, array $context ) — before void/cancel API call.
  • fabrick_orch_cancel_success( WC_Order $order, array $response ) — void/cancel succeeded.
  • fabrick_orch_cancel_failed( WC_Order $order, array $response, Throwable|null $error ) — void/cancel failed.
  • fabrick_orch_payment_token_created( WC_Payment_Token $token, WC_Order $order, array $detail ) — new saved card token persisted.
  • fabrick_orch_payment_token_updated( WC_Payment_Token $token, WC_Order $order, array $detail ) — existing token updated.
  • fabrick_orch_payment_token_deleted( WC_Payment_Token $token ) — token removed locally (before WC delete).
  • fabrick_orch_remote_token_deleted( WC_Payment_Token $token, array $payload ) — token deleted remotely on Orchestra ( DELETE shop/token ).
  • fabrick_orch_oneclick_submitted( array $submitted, WC_Order $order, WC_Payment_Token $token ) — OneClick submit completed.
  • fabrick_orch_legacy_token_migrated( WC_Payment_Token $token, int $user_id, array $card ) — legacy GestPay token migrated (only if migration is enabled).
  • fabrick_orch_subscription_renewal_success( WC_Order $renewal_order, array $payment_detail, object|null $subscription ) — WCS renewal succeeded.
  • fabrick_orch_subscription_renewal_failed( WC_Order $renewal_order, string $message, object|null $subscription ) — WCS renewal failed.
  • fabrick_orch_pay_by_link_generated( WC_Order $order, string $redirect_url, string $payment_id ) — Pay By Link session created.
  • fabrick_orch_pay_by_link_email_sent( WC_Order $order, string $recipient ) — Pay By Link email sent to buyer.
  • gestpay_on_renewal_payment_failure( … ) — deprecated alias of fabrick_orch_subscription_renewal_failed.

Filters — payment/create & API

  • fabrick_orch_alter_order_id( string $shop_transaction_id, WC_Order $order, array $context ) — external shop transaction ID sent to Orchestra.
  • fabrick_orch_order_details( array $details, WC_Order $order ) — OrderDetails block (Klarna / APM).
  • fabrick_orch_ecommerce_trans_details( array $details, WC_Order $order ) — ecommerce transDetails ( type=EC ) for one-shot create; subscription First replaces this with MIT 01F.
  • fabrick_orch_create_payment_request( array $payload, WC_Order $order, array $context ) — checkout payment/create body (includes first-level CMS metadata: CMS_Type, CMS_Version, Module_Version, WP_Version ).
  • fabrick_orch_pay_by_link_create_request( array $payload, WC_Order $order ) — Pay By Link payment/create body (same CMS metadata).
  • fabrick_orch_payment_language_id( string $language_id, WC_Order $order, array $context ) — languageId sent in checkout and Pay By Link payment/create ( '1' Italian, '2' English, '3' Spanish, '4' French, '5' German; return '' to omit it). $context: source, locale.
  • fabrick_orch_available_payment_methods( array $methods, WC_Order|null $order, array $context ) — paymentType codes included in create.
  • fabrick_orch_api_request_params( array $params, string $endpoint, string $method, WC_Order|null $order ) — Orchestra REST request body/query.
  • fabrick_orch_api_request_headers( array $headers, string $endpoint, string $method, array $params, WC_Order|null $order ) — REST headers.
  • fabrick_orch_api_request_response( array|WP_Error $response, string $method, string $url, string $endpoint ) — raw HTTP response.

Filters — callback, checkout UI, Blocks

  • fabrick_orch_revert_order_id( string $order_id, array $callback_params, string $source ) — map callback reference back to WooCommerce order ID.
  • fabrick_orch_process_callback_async( bool $async, WC_Order $order, string $source, array $params ) — defer callback to Action Scheduler.
  • fabrick_orch_callback_deferred_delay( int $seconds, … ) — delay when callback is deferred.
  • fabrick_orch_buyer_ok_retry_attempts( int $attempts ) — buyer return retry count.
  • fabrick_orch_buyer_ok_retry_delay_seconds( int $seconds ) — delay between buyer return retries.
  • fabrick_orch_webcomponent_attributes( array $attributes, WC_Order $order, array $context ) — <fbk-checkout> HTML attributes.
  • fabrick_orch_checkout_script_params( array $params, WC_Order $order ) — pay-page JavaScript bootstrap.
  • fabrick_orch_pay_page_script_config( array $config, WC_Order $order ) — pay-page UX script config.
  • fabrick_orch_blocks_payment_method_data( array $data, object $gateway ) — WooCommerce Blocks payment method data.
  • fabrick_orch_is_blocks_checkout_supported( bool $supported ) — whether Blocks integration is active.

Filters — refunds, tokens, subscriptions, settings, logging

  • fabrick_orch_refund_request( array $payload, WC_Order $order, float|null $amount, string $reason ) — refund API payload.
  • fabrick_orch_cancel_request( array $payload, WC_Order $order ) — void/cancel API payload.
  • fabrick_orch_oneclick_submit_body( array $body, WC_Order $order, string $orchestra_token ) — OneClick payment/submit body.
  • fabrick_orch_saved_card_display_label( string $label, WC_Payment_Token $card ) — My Account saved card label.
  • fabrick_orch_legacy_token_migration_enabled( bool $enabled ) — opt-in legacy token import (default false ).
  • fabrick_orch_mit_payment_request( array $payload, WC_Order $renewal_order, WC_Payment_Token $token ) — MIT renewal create payload (includes CMS metadata).
  • fabrick_orch_mit_authentication_amount( float $amount, WC_Order $order, string $recurring_total ) — First authentication amount (default recurring × 1.25).
  • fabrick_orch_mit_recurring_frequency( int $days, WC_Order $order ) — days between recurring charges.
  • fabrick_orch_settings_fields( array $fields, object $gateway ) — gateway settings fields.
  • fabrick_orch_shop_methods( array $methods, string $environment, bool $from_cache ) — terminal methods catalog entries.
  • fabrick_orch_shop_methods_cache_ttl( int $seconds, string $environment ) — catalog cache TTL.
  • fabrick_orch_methods_refresh_diff( object $diff, string $environment ) — diff after methods refresh.
  • fabrick_orch_methods_reconciliation_notice( bool $show, array $missing_types ) — admin notice for missing methods.
  • fabrick_orch_method_logo_url( string $url, string $code, string $label ) — payment method logo URL in settings.
  • fabrick_orch_logging_enabled( bool $enabled, string $level, string $message, array $context ) — enable/disable plugin logging.
  • fabrick_orch_log_context( array $context, string $level, string $message ) — mask or enrich log context.
  • fabrick_orch_mask_log_value( string $masked, string $key, mixed $value ) — mask a single log value.
  • fabrick_orch_debug_enabled( bool $enabled ) — force debug mode on/off.
  • fabrick_orch_debug_log_max( int $max ) — admin debug log buffer size ( 0 disables the buffer).
  • gestpay_revert_order_id( mixed $order_id ) — deprecated alias of fabrick_orch_revert_order_id (order ID resolution only).
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • credit card
  • payment gateway
  • fabrick
  • subscriptions
  • woocommerce
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.4 · PHP 8.0
Update activity29 Oct 20264d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.0.01.0.2
WordPress compatibility7.1.37.1.4
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.