WooCommerce
Maintains the commercial order, checkout context, products, totals, currency, and final order payment state.
GPCB Pay is an independently developed payment integration for WooCommerce, connecting your store to supported PayPal-powered card payment experiences through a private SaaS Payment Core.
Our focus is straightforward: trusted payment verification, clear system responsibilities, and responsible handling of interrupted payment operations.
GPCB Pay stands for General PayPal Card Bridge. It is a commercial integration designed to help WooCommerce merchants connect supported PayPal card payment experiences to their stores.
The product combines a lightweight WooCommerce Connector with a private SaaS service responsible for trusted payment coordination.
GPCB Pay does not replace WooCommerce, operate as an independent payment processor, or take over the merchant's PayPal account.
The merchant retains control of the WooCommerce store and uses their own eligible PayPal Business account.
Payment integration is about more than displaying a payment option at checkout.
A customer may approve a payment while a network interruption prevents the store from receiving the final response. Repeated requests can also introduce uncertainty unless the original payment attempt is tracked carefully.
GPCB Pay was built around the idea that payment completion should be supported by verified evidence, not assumptions.
By separating WooCommerce commercial authority from server-side PayPal payment coordination, the integration aims to make these boundaries explicit and easier to maintain.
The integration is built around explicit boundaries between the store, the SaaS service, and the payment provider.
Maintains the commercial order, checkout context, products, totals, currency, and final order payment state.
Coordinates authenticated payment requests, PayPal order creation, verified capture, idempotency, and supported recovery.
Provides the applicable payment services and hosted card-entry experiences according to merchant eligibility and provider requirements.
PayPal approval alone does not authorize WooCommerce to mark an order paid. Payment completion depends on trusted server-side capture verification.
These principles guide the design of GPCB Pay's payment integration and its handling of uncertain payment outcomes.
A browser message or payment approval is not proof of completed payment. WooCommerce completion requires trusted, verified capture evidence.
WooCommerce owns the commercial order. GPCB Pay coordinates trusted payment operations. PayPal remains the payment provider.
Sensitive merchant credentials belong within protected server-side workflows, not public browser code or customer-facing pages.
Durable request identities and idempotency safeguards help prevent unnecessary repeated payment capture operations.
Payment attempts are tracked using persisted state so supported interruptions can be evaluated against the original payment identity.
When sufficient trusted payment evidence is unavailable, the system must not declare an order paid based on assumptions.
Merchants should understand what the integration provides, what it depends on, and where its responsibilities end.
GPCB Pay is independently developed. It is not an official PayPal or WooCommerce product and is not endorsed by either.
PayPal and WooCommerce remain separate products with their own requirements, terms, and responsibilities.
GPCB Pay does not independently process card transactions or act as a merchant of record. Supported payments use the merchant's own PayPal Business relationship.
Applicable PayPal processing fees are separate from GPCB Pay SaaS charges.
Guest Card availability depends on PayPal requirements, the merchant account, and the checkout context.
Advanced Card Payments require specific PayPal merchant eligibility and approval. They are not available universally.
The WooCommerce Connector communicates with the private GPCB Pay SaaS Payment Core.
The Connector is separate from paid SaaS access. Service interruptions may affect payment availability, and recovery cannot be guaranteed in every case.
Supported card-entry experiences use PayPal-hosted payment interfaces. The Connector and GPCB Pay SaaS are not designed to collect or store buyers' complete card numbers or CVV.
Learn about our security modelGPCB Pay was founded and developed by Rachid Attia, an independent software developer and digital entrepreneur based in Morocco.
The project grew from a focus on solving real WooCommerce payment integration challenges. Its development emphasizes clear system responsibilities, trusted payment verification, and durable payment state.
As an independently developed product, GPCB Pay aims to build merchant trust through transparent documentation, responsible engineering, and clear communication about its capabilities and limitations.
Independent software developer and founder of GPCB Pay. Based in Morocco.
Building practical software solutions with an emphasis on reliability, verification, and responsible system design.
Review the technical documentation, understand the supported payment experiences, and explore the available merchant onboarding process.
Questions about integration or eligibility? Contact GPCB Pay Support