Title: GPCB Pay – Card Payments for WooCommerce
Author: Rachid Attia
Published: <strong>November 17, 2026</strong>
Last modified: November 17, 2026

---

Search plugins

![](https://ps.w.org/gpcb-pay-card-payments-for-woocommerce/assets/banner-772x250.
png?rev=3807987)

![](https://ps.w.org/gpcb-pay-card-payments-for-woocommerce/assets/icon-256x256.
png?rev=3807987)

# GPCB Pay – Card Payments for WooCommerce

 By [Rachid Attia](https://profiles.wordpress.org/rachidattia/)

[Download](https://downloads.wordpress.org/plugin/gpcb-pay-card-payments-for-woocommerce.0.1.0.zip)

 * [Details](https://wordpress.org/plugins/gpcb-pay-card-payments-for-woocommerce/#description)
 * [Reviews](https://wordpress.org/plugins/gpcb-pay-card-payments-for-woocommerce/#reviews)
 *  [Installation](https://wordpress.org/plugins/gpcb-pay-card-payments-for-woocommerce/#installation)
 * [Development](https://wordpress.org/plugins/gpcb-pay-card-payments-for-woocommerce/#developers)

 [Support](https://wordpress.org/support/plugin/gpcb-pay-card-payments-for-woocommerce/)

## Description

GPCB Pay – Card Payments for WooCommerce is a free, open-source WooCommerce Checkout
Blocks payment connector. It integrates eligible PayPal-hosted debit and credit 
card experiences with an external, managed GPCB Pay SaaS Payment Core.

The plugin is free to install. The required external GPCB Pay SaaS is a separate
service and may require an eligible trial or paid subscription. PayPal processing
fees are separate. The plugin cannot process payments without its SaaS dependency.

GPCB Pay is independently developed. It is not affiliated with, sponsored by, or
endorsed by PayPal or WooCommerce.

#### Supported Payment Modes

 * Guest Card: Eligible PayPal-hosted guest card checkout, depending on PayPal merchant,
   country, account and checkout-context eligibility.
 * Advanced Card: PayPal-hosted Advanced Card Fields, available only when PayPal
   grants the merchant the necessary capabilities and approval.
 * Auto: Not supported in version 0.1.0. Select Guest or Advanced explicitly; automatic
   switching is not implemented.

GPCB Pay cannot override PayPal eligibility or guarantee that a payment method appears
for every merchant or buyer.

#### Main Features

 * WooCommerce Checkout Blocks integration, with Guest and Advanced payment adapters.
 * PayPal JavaScript SDK v6 integration and PayPal-hosted card entry.
 * Sandbox and Live configuration and browser-safe PayPal initialization.
 * HMAC-authenticated Connector communication with the private SaaS.
 * Server-derived WooCommerce order amount, currency and commercial fingerprint.
 * SaaS-controlled PayPal Order creation and server-verified Capture.
 * Durable payment state, idempotency, duplicate-Capture safeguards, recovery and
   reconciliation.
 * Merchant, store and subscription authorization boundaries.
 * Advanced Card layouts: Clean, Compact and Premium.
 * Admin connection diagnostics, DNS ownership verification and provisioning-store
   Connector proof.

#### Payment Security Architecture

WooCommerce is the authority for its orders, totals, currencies and order-completion
operations. The Connector sends authenticated server-to-server requests to the GPCB
Pay SaaS. The SaaS manages merchant PayPal credentials, PayPal Order/Capture operations
and durable payment evidence.

Browser approval is not proof of payment. Creating a PayPal Order is not proof of
payment. Only a successful server-verified Capture allows the WooCommerce order 
to be completed. Payment attempts with uncertain outcomes may need verification 
or reconciliation; never initiate a blind duplicate Capture.

Merchant identity, domain ownership, Connector proof, PayPal eligibility, store 
activation and subscription entitlement are distinct checks. Passing one does not
authorize the others. A successful diagnostic does not establish successful payment
or Live checkout readiness.

Card details are entered using PayPal-hosted components. The Connector is not designed
to collect or store raw card numbers, CVV or complete expiry details. Merchants 
remain responsible for their applicable privacy, security and regulatory obligations.

### Requirements

 * WordPress 7.1 or later and PHP 8.2 or later.
 * WooCommerce 11.1.2 or later; verify compatibility before upgrades.
 * WooCommerce Checkout Blocks and HTTPS on the WooCommerce website.
 * Verified GPCB Pay merchant account, authorized store and saved Connector Key 
   ID / Signing Secret.
 * Verified DNS domain ownership and provisioning-store Connector connection proof.
 * Completed SaaS store activation and securely configured merchant PayPal credentials.
 * PayPal eligibility for the explicitly selected mode and valid SaaS service authorization.

Version 0.1.0 is designed for Checkout Blocks only. Classic shortcode checkout is
not supported in this release.

### SaaS Subscription and Fees

The WordPress Connector is open-source under GPLv2 or later. The external GPCB Pay
SaaS is a separate paid service providing operational payment infrastructure, not
a license key to unlock plugin source code.

 * Pro monthly: USD $19.
 * Pro yearly: USD $190.
 * Eligible one-time trial: 7 consecutive days (168 hours).
 * Renewal: Manual; automatic recurring billing is not included in version 0.1.0.
 * Store allowance: One authorized WooCommerce website per merchant account. No 
   three-store tier in version 0.1.0.
 * Separate PayPal processing fees apply.

Store activation, trial and paid entitlement are independently authorized. Where
enforcement applies, expired service access prevents new payment initialization,
while existing payment recovery remains separately controlled. Current terms and
pricing: https://gpcbpay.com/

### External Services and Data Disclosure

This plugin requires both the GPCB Pay SaaS and PayPal to provide its payment functionality.
Review their terms and privacy policies before using it.

#### GPCB Pay SaaS

Provider: GPCB Pay
 Website: https://gpcbpay.com/ Merchant Dashboard: https://app.
gpcbpay.com/ Published API: https://api.gpcbpay.com/ Connector API origin for version
0.1.0: https://general-payment-bridge-saas-production.up.railway.app/ Privacy Policy:
https://gpcbpay.com/privacy-policy/ Terms of Service: https://gpcbpay.com/terms-
of-service/

The Connector contacts the SaaS when an administrator explicitly runs diagnostics
or when checkout, payment, Capture, verification or recovery requires it. The SaaS
authenticates Connector requests, associates them with an authorized store, manages
protected merchant PayPal credentials, coordinates Orders and Captures, stores durable
payment evidence, supports reconciliation and evaluates subscription authorization.

Data sent, depending on operation, may include Connector identifiers, signed authentication
metadata, WooCommerce order references, server-derived amounts/currencies, selected
payment mode and environment, PayPal Order/Capture references, payment states and
recovery identifiers. Separate Dashboard onboarding/billing workflows may collect
merchant account information, store domain, verification data, protected PayPal 
credentials and subscription information.

The Connector does not send raw card numbers or CVV to the SaaS. Applicable handling
and retention are described in the privacy policy.

#### PayPal

Provider: PayPal
 Website: https://www.paypal.com/ Privacy information: https://
www.paypal.com/privacy-center/

PayPal provides hosted card-entry components and payment processing. The buyer’s
browser communicates with PayPal-hosted components. PayPal may process cardholder,
billing, contact, authorization and risk-assessment information. The GPCB Pay SaaS
calls PayPal APIs for eligible Order, Capture and verification operations. PayPal
determines merchant eligibility and method availability.

## Installation

Follow the onboarding sequence below. Store ownership, Connector verification, PayPal
eligibility, store activation, subscription authorization, and successful payment
are separate conditions. Do not accept customer-facing Live payments until the applicable
requirements are satisfied.

#### Step 1: Prepare WooCommerce

 1. Install and activate WooCommerce.
 2. Configure the WooCommerce store.
 3. Confirm that your website uses HTTPS.
 4. Configure a WooCommerce Checkout Blocks checkout page.
 5. Install and activate GPCB Pay – Card Payments for WooCommerce.

#### Step 2: Create Your GPCB Pay Account

 1. Open the Merchant Dashboard: https://app.gpcbpay.com/
 2. Register or sign in.
 3. Complete merchant email verification.
 4. Open the store management section.

Registration does not automatically activate a store, start a trial, or authorize
payment processing.

#### Step 3: Add Your WooCommerce Store

 1. Choose the available action for adding a WooCommerce store.
 2. Follow the Merchant Dashboard provisioning instructions.
 3. Save the SaaS Store ID for reference.
 4. Securely copy the Connector Key ID.
 5. Securely copy the Connector Signing Secret, which may only be displayed once.

The Signing Secret is sensitive. Never publish it in a repository, screenshot, or
support request. If lost, use authorized credential recovery, which may invalidate
previous credentials. Do not rotate because a network operation timed out. The initial
Pro plan allows one authorized website; provisioning or suspended stores may occupy
the store slot.

#### Step 4: Configure the WooCommerce Connector

 1. Open the WordPress administration dashboard.
 2. Go to WooCommerce > Settings > Payments.
 3. Open the GPCB Pay gateway settings.
 4. Enter the Connector Key ID.
 5. Enter the Connector Signing Secret.
 6. Select Sandbox or Live.
 7. Select explicit Guest Card or Advanced Card mode.
 8. Save the gateway settings before testing the connection.

Connector credentials are not PayPal API credentials. Never put a PayPal Client 
Secret in WooCommerce Connector settings. Saving credentials does not prove SaaS
store activation.

#### Step 5: Verify Domain Ownership

 1.  Return to the Merchant Dashboard.
 2.  Select the provisioning store.
 3.  Open the domain verification workflow.
 4.  Enter the actual hostname, such as shop.example.com (not https://shop.example.
     com/checkout/).
 5.  Generate the DNS TXT verification challenge.
 6.  Open DNS management for your domain.
 7.  Add the exact TXT host and value specified by the dashboard.
 8.  Allow time for DNS propagation.
 9.  Return to the Merchant Dashboard.
 10. Complete DNS verification through the SaaS.

Only SaaS-verified DNS evidence establishes the required hostname control. Browser-
entered values are not proof. If the challenge expires, obtain fresh evidence through
the authorized workflow.

#### Step 6: Verify Your New Store Connection

 1. Return to WordPress.
 2. Open the GPCB Pay gateway settings.
 3. Locate GPCB Pay — Store Connection Setup.
 4. Find Step 1 — Verify Your New Store Connection.
 5. Click Verify New Store Connection for the provisioning store.

The WordPress server sends an HMAC-signed request proving possession of saved Connector
credentials. The private SaaS records short-lived proof separately from DNS verification.
This proof expires within 15 minutes. Repeat the verification if necessary; do not
rotate credentials or recreate the store due to expiration.

This action does not independently verify DNS, activate a store, start a trial, 
grant subscription access, or create/Capture a PayPal payment.

#### Step 7: Complete Store Activation

 1. Return to the Merchant Dashboard.
 2. Select the provisioning store.
 3. Confirm completed DNS ownership and Connector verification.
 4. Complete the authorized verified-store activation workflow.

The SaaS checks merchant identity, ownership, lifecycle status, current credential,
and applicable admission requirements. Activation does not automatically start a
trial or subscription. Do not bypass disabled controls.

#### Step 8: Test Your Active SaaS Connection

 1. Return to WooCommerce gateway settings.
 2. Locate GPCB Pay — Store Connection Setup.
 3. Find Step 2 — Test Your Active SaaS Connection.
 4. Click Test SaaS Connection after the SaaS reports the store active.

The active-store diagnostic is different from provisioning proof. Neither test creates/
Captures a payment, proves PayPal eligibility, or grants subscription access.

#### Step 9: Configure Merchant PayPal Credentials

 1. Open the Merchant Dashboard.
 2. Locate the PayPal merchant connection settings.
 3. Follow the authorized secure credential workflow.
 4. Supply the required PayPal Business credentials to the SaaS-controlled form.
 5. Save the PayPal configuration through the secure SaaS process.

The private SaaS protects merchant credentials; the Connector does not need PayPal
Client Secrets in WordPress. Never expose secrets or OAuth tokens in JavaScript,
screenshots, public code, or ordinary support messages. PayPal determines Advanced
and Guest availability.

#### Step 10: Confirm Payment Readiness

 1. Confirm the SaaS store is active.
 2. Confirm the configured payment environment.
 3. Confirm PayPal eligibility for the selected explicit payment mode.
 4. Complete the applicable readiness and service-access requirements.
 5. Use the appropriate Sandbox administrator diagnostics and test an unpaid checkout
    order.

A Sandbox success does not establish Live eligibility. The SaaS Create Order diagnostic
may create a Sandbox PayPal Order, but does not Capture it or mark WooCommerce paid.
Test server-verified Capture separately before Live use.

#### Step 11: Start Your Eligible Trial

An eligible one-time seven-day trial starts only when a separate authorized SaaS
activation succeeds. Registration and store activation do not start it. The trial
lasts 168 consecutive hours, does not automatically pause, and provides managed 
service access rather than locked WordPress plugin code. Check its recorded start/
end and access status in the Merchant Dashboard.

#### Step 12: Maintain Pro Subscription Access

The initial Pro offering is USD $19/month or $190/year, with manual renewal, one
authorized WooCommerce website and a separate eligible one-time trial. PayPal processing
fees are additional. Creating or approving a subscription PayPal Order is not proof
of payment; verified SaaS billing evidence and authorized entitlement are required.
Where enforced, expiration blocks new payment initialization; existing durable payment
attempts retain their separate recovery handling. See https://gpcbpay.com/ for current
terms.

#### Troubleshooting and Safe Recovery

 * Check merchant verification, store ownership and the configured Connector Key
   ID / Signing Secret.
 * Check DNS TXT record, proof expiry, provisioning versus active store status and
   SaaS availability.
 * Check the saved Sandbox/Live environment, explicitly selected mode, PayPal merchant
   eligibility and service entitlement.
 * For pending proof failure, re-verify while provisioning; for an active store,
   use the active connection test.
 * After uncertain Create Order, Capture or billing results, verify/reconcile the
   original attempt. Never blindly repeat financial operations.
 * Do not create replacement stores or rotate credentials solely because of a timeout.

Support: https://gpcbpay.com/ or support@gpcbpay.com

Do not send passwords, raw card data, Connector Signing Secrets, PayPal Client Secrets
or OAuth tokens in ordinary support requests.

## FAQ

### Is the plugin free and can it process payments without the SaaS?

The Connector is free and open-source. It cannot process payments without the required
external SaaS, which may require trial or paid access; PayPal processing fees remain
separate.

### Does it work with Classic Checkout or automatic Guest/Advanced switching?

No. Version 0.1.0 supports Checkout Blocks with an explicitly configured Guest or
Advanced mode. Auto switching and Classic shortcode checkout are not supported.

### Are Guest and Advanced Card available everywhere?

No. PayPal decides availability. Advanced requires merchant approval and capabilities.
Guest availability depends on merchant and checkout context.

### Why are DNS and Connector verification separate?

DNS verifies hostname control; HMAC Connector proof verifies possession of saved
signing credentials. Neither alone activates a store or authorizes a payment. New-
store Connector proof expires after 15 minutes.

### Which diagnostic should I run?

Use Verify New Store Connection while provisioning. After SaaS activation, use Test
SaaS Connection. Neither diagnostic creates or Captures a payment.

### Does activation start my trial or enable paid access?

No. Merchant registration, store activation, trial activation and paid entitlement
are separate. The eligible trial begins only after its authorized activation and
runs for 168 hours.

### Can I use three stores or release a store slot by uninstalling?

The initial Pro plan covers one site. Uninstalling does not release an independently
managed SaaS store slot; a three-site plan is not included in version 0.1.0.

### Where should PayPal API credentials be entered?

Use the authorized Merchant Dashboard workflow. Do not enter a PayPal Client Secret
into the Connector’s WordPress settings.

### Is PayPal browser approval proof that an order is paid?

No. Only server-verified Capture can authorize WooCommerce completion. Uncertain
results require verification/reconciliation rather than blind retries.

### Is renewal automatic and are PayPal fees included?

No. The initial SaaS offering renews manually; PayPal processing fees are separate
from GPCB Pay subscriptions.

### Is GPCB Pay affiliated with PayPal or WooCommerce?

No. GPCB Pay is an independent integration using eligible PayPal payment services.

### Where can I get support?

https://gpcbpay.com/ — support@gpcbpay.com

Never share signing secrets, cardholder data, PayPal Client Secrets or OAuth tokens
in ordinary messages.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“GPCB Pay – Card Payments for WooCommerce” is open source software. The following
people have contributed to this plugin.

Contributors

 *   [ Rachid Attia ](https://profiles.wordpress.org/rachidattia/)

[Translate “GPCB Pay – Card Payments for WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/gpcb-pay-card-payments-for-woocommerce)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/gpcb-pay-card-payments-for-woocommerce/),
check out the [SVN repository](https://plugins.svn.wordpress.org/gpcb-pay-card-payments-for-woocommerce/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/gpcb-pay-card-payments-for-woocommerce/)
by [RSS](https://plugins.trac.wordpress.org/log/gpcb-pay-card-payments-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.1.0

 * Initial WooCommerce Checkout Blocks Connector with eligible Guest and Advanced
   Card modes.
 * Added authenticated private SaaS Payment Core and PayPal-hosted card entry.
 * Added server-derived commercial assertions, server-verified Capture and durable
   payment evidence.
 * Added idempotency, duplicate-Capture safeguards, recovery and reconciliation 
   support.
 * Added Sandbox/Live configuration, Advanced Card layouts and admin diagnostics.
 * Documented merchant onboarding, DNS/Connector verification, trial, pricing and
   external services.

## Meta

 *  Version **0.1.0**
 *  Last updated **1 hour ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 7.1 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 8.2 or higher **
 * Tags
 * [checkout](https://wordpress.org/plugins/tags/checkout/)[credit card](https://wordpress.org/plugins/tags/credit-card/)
   [payments](https://wordpress.org/plugins/tags/payments/)[paypal](https://wordpress.org/plugins/tags/paypal/)
   [woocommerce](https://wordpress.org/plugins/tags/woocommerce/)
 *  [Advanced View](https://wordpress.org/plugins/gpcb-pay-card-payments-for-woocommerce/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/gpcb-pay-card-payments-for-woocommerce/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/gpcb-pay-card-payments-for-woocommerce/reviews/)

## Contributors

 *   [ Rachid Attia ](https://profiles.wordpress.org/rachidattia/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/gpcb-pay-card-payments-for-woocommerce/)