BrickellPay Gateway for WooCommerce

script-src  'self' https://payments.brickellpay.com https://code.ionia.app https://js.verygoodvault.com;
frame-src   'self' https://code.ionia.app https://*.verygoodvault.com;
connect-src 'self' https://payments.brickellpay.com <your-merchant-API-URL>;
img-src     'self' data: https://payments.brickellpay.com;

Changelog

1.0.13

• Fixed: terms and conditions consent is now recorded before the first card is added, so the acceptance is captured for every checkout rather than only for those that reach the card step.
• Fixed: consent is also captured on the inline cardless route, which previously completed without recording it.
• Fixed: a new user is no longer asked to accept the terms twice during a single checkout.

1.0.12

• Fixed: release 1.0.11 was built from a branch that predated the 1.0.10 review fixes, so several of them were absent from the submitted package even though they had already been made. This release carries them forward. Specifically restored: the bundled intl-tel-input library at v29.2.2 (1.0.11 shipped v18.2.1 again), the == External services == disclosure covering IoniaPay, the correct Contributors username, the removal of the Plugin URI header, and the per-field schema sanitization of the test-mode create-user request body.
• Removed: the empty assets/js/vendor/intl-tel-input/build/ directory left behind when the library moved to dist/.
• Fixed: the distribution package no longer contains .htaccess. WordPress.org does not permit hidden files in an uploaded plugin, and the file guards nothing in that package — everything it denies access to (.env and dev files) is already excluded from it. It remains in the repository for manually deployed installs, where it does protect those files.
• Changed: Tested up to raised to 7.1.

1.0.11

• Added: Requires Plugins: woocommerce header, so WordPress verifies the WooCommerce dependency before activation.
• Fixed: the sandbox API endpoint shipped with a local development default. Distributed builds now point at the public sandbox host.
• Fixed: in API tokenization mode the card fields rendered without labels or placeholders and in the wrong order. They now match the surrounding billing fields, with cardholder and card number full width and expiry and CVC side by side.
• Fixed: the expiry field now inserts the / separator as the customer types. Entering the digits without it was rejected during tokenization and surfaced as a generic card error.
• Fixed: a returning customer with no saved card reached a dead end after identity verification. The card form is now shown instead.
• Fixed: a saved card that cannot be selected no longer blocks adding the same card again.
• Fixed: checkout could stop listening for the verification result if the payment session identifier had not yet arrived, leaving the customer on the verification screen with no error.
• Changed: when the tokenization mode is not the hosted iframe, the checkout now records it to the store log instead of proceeding silently.
• Security: certificate verification enforced on all outbound requests; environment files blocked from HTTP access; test-mode-only flags are no longer honored outside test mode.

1.0.10

• Added: full disclosure of IoniaPay (IoniaPay, LLC) as a third-party external service in the readme, covering both the browser-loaded code.ionia.app SDK/Terms host and the server-side ioniapay.ionia.app saved-card fallback, what data is sent to each and when, and links to IoniaPay’s terms of service and privacy policy.
• Fixed: the readme incorrectly stated that the tokenization/verify SDK modules are fetched from the BrickellPay facade host. They are loaded from the Ionia CDN; corrected and cross-referenced.
• Changed: updated the bundled intl-tel-input library from v18.2.1 to v29.2.2. This is an API migration, not a version bump — v25 removed isPossibleNumber() and swapped the meaning of the remaining validators, so the checkout phone gate now reads strict validation from isValidNumberPrecise() and keeps isValidNumber() for the sandbox-only relaxation. Reading the new API as if it were the old one would have silently downgraded live phone validation to a length-only check. Also migrated preferredCountries to countryOrder and dropped the separate utilsScript fetch in favour of the bundled “WithUtils” build.
• Changed: declared intl-tel-input in the readme’s bundled-libraries list, and documented the test-mode-only local copy of the tokenization facade.
• Fixed: the thank-you page shipping-address correction no longer prints an inline <script> block; it is registered through wp_enqueue_script with its data passed via wp_localize_script.
• Security: the brickellpay_create_user AJAX body (test mode only) is now rebuilt field by field against its expected schema instead of being forwarded as a decoded blob. Unknown keys are dropped, text fields are sanitized, numeric fields are reduced to digits, and required fields are enforced before any upstream call.
• Fixed: the Plugin URI header pointed at a page that returned 404. There is no plugin-specific landing page to point it at, and WordPress.org rejects a Plugin URI that duplicates Author URI, so the header has been removed — Author URI alone now carries the link. The support link in the FAQ was likewise a 404 and now points at an existing page.
• Fixed: Contributors now lists the plugin owner’s actual WordPress.org username.

1.0.9

• Fixed: the card form failed to load with a 404 on tokenization-1.0.4.min.js. The self-hosted SDK directory that URL pointed at has been retired — no version resolves there any more — so the plugin now requests SDK 1.0.5 and pins the SDK origin to Ionia’s CDN instead of inheriting whichever default the tokenization facade happens to ship with. Both values remain overridable by env var or filter.

1.0.8

• Changed: migrated the Ionia card-tokenization facade to v2 (Ionia SDK 1.0.5). The card-form mount now requires and passes a JWT, matching the facade’s new contract; behavior is unchanged for shoppers.

1.0.7

• Fixed: a KYC 10099 notification that carries a failure flag is no longer swallowed by the generic transaction-failure handler before its recovery can run. Specific KYC status codes are now dispatched ahead of the generic catch-all, so recovery (user-verify retry) fires as intended. Retains the 1.0.6 diagnostics.

1.0.6

• Fixed: the checkout error-message lookup (admin-ajax brickellpay_get_error_message) is now registered early, so it no longer returns an unregistered-action “0”/400 on requests that don’t instantiate the gateway.
• Diagnostic: added non-invasive breadcrumb logging across the SignalR-notification and 10099-recovery path (window.brickellpayDumpDiag()), to pinpoint where the 10099 recovery bails in real (SignalR-connected) environments. No behavior change to the payment flow.

1.0.5

• Fixed: Resend Code (AZ #2339) fired a request that Ionia rejected with HTTP 400, with no resend ever reaching Ionia’s logs. The button’s own click handlers were resolving a stale payment token as the auth bearer instead of the session token when the auth session had expired, bypassing an earlier fix made deeper in the same code path.

1.0.4

• Fixed: a real KYC 10099 notification arriving while a speculative card-fetch was already in flight got silently dropped, leaving checkout stuck with no retry and no charge attempt (AB#1/AB#2). The coalesced notification is now queued and replayed once the in-flight attempt resolves.

1.0.3

• Fixed: removed all remaining error_log() calls (Plugin Check flags the call itself regardless of any surrounding debug-only guard) — the plugin already treats logging as disabled-for-security elsewhere, so these were inconsistent with that policy anyway.
• Fixed: a phpcs:ignore comment used a non-standard dash character and was silently not suppressing its target warning; corrected to the standard delimiter with a clearer rationale.

1.0.2

• Fixed: text domain now matches the assigned plugin slug (brickellpay-gateway-for-woocommerce) so translations load correctly.
• Fixed: removed a discouraged, unnecessary translation-loading call (WordPress.org loads plugin translations automatically).
• Housekeeping: debug logging now only fires when WP_DEBUG is enabled; added missing translator comments; minor input-sanitization hardening.

1.0.1

• Fixed: KYC 10099 recovery could abort with “incomplete data” and never retry, when an earlier card-less status push had already consumed the one-time retry.
• Fixed: existing-user SMS verification now sends at Validate instead of only at Place Order.
• Fixed: terms & conditions “read more” link now opens in a new tab instead of being inert.
• Fixed: new-user checkout now defaults the billing country to United States.
• Fixed: billing phone field label no longer shows a lingering “(optional)” suffix.
• Fixed: the “Processing your payment…” loader no longer gets stuck on screen when a checkout error is shown.
• Fixed: the “X is a required field” notice now clears once the field is filled in.
• Fixed: the Resend Code button no longer risks sending the wrong token type on retry.

1.0.0

• Initial public release.
• WooCommerce HPOS support.
• Card tokenization, sale/auth/capture, refund, void.
• Smart routing with automatic processor failover.
• Real-time SignalR notifications.
• WooCommerce Subscriptions integration.