E‑commerce integrations

These extensions keep providers, routing, and webhooks in Payment Gateway App while your store shows a single payment method at checkout. Configure each plugin with your Admin API hostname (ADMIN_BACKEND_DOMAIN — no https:// in the plugin field; hosted: api.payment-gateway.app), Site ID, an API key with the checkout:create scope shown in Admin → API Keys, and the Webhook Signing Secret from Sites → Edit Site (used to verify IPN signatures). The plugin registers its own IPN URL on the store side; the gateway posts signed notifications to that URL when transaction status changes. See Hostnames & DNS conventions.

Full product documentation lives at docs.payment-gateway.app, including API references and IPN verification details.

WooCommerce

• Repository: payment-gateway-plugin-woocommerce (official WooCommerce extension)
• Typical setup: install the plugin ZIP, then WooCommerce → Settings → Payments → Payment Gateway App — set API domain (no https://), Site ID, API key, and Webhook Signing Secret (whsec_…).
• Inbound IPN: the plugin registers [your-store]/wc-api/wc_payment_gateway_app and verifies X-Signature-Timestamp + X-Signature-HMAC-SHA256 (same scheme as the core outbound IPN described in Webhooks & IPN).
• Checkout errors: gateway checkout failures are shown with customer-safe text and the gateway requestId when present. Unresolved disputes use CHECKOUT_BLOCKED_BY_DISPUTE; final merchant-loss Customer Risk Holds use CHECKOUT_BLOCKED_BY_CUSTOMER_HOLD or CHECKOUT_RESTRICTED_BY_CUSTOMER_HOLD when only safe bank-transfer methods are allowed.
• Debug logs: enable WooCommerce Debug Log only while troubleshooting. The plugin logs support-safe gateway metadata such as code, request ID, transaction reference, dispute ID, and customer-risk-hold reference instead of raw checkout payloads.

aMember Pro

• Repository: payment-gateway-plugin-amember (official aMember Pro extension)
• Requirements: aMember Pro 6.3+, PHP 8.2+, and a running Payment Gateway App instance.
• Typical setup: upload the plugin per the README, enable it under Configuration → Plugins, then Configuration → Setup/Configuration → Payment Gateway App — same core fields as WooCommerce (API domain, Site ID, API key, Webhook Signing Secret).
• Inbound IPN: [your-amember-url]/payment/payment-gateway-app/ipn with the same signature headers; the plugin applies replay protection on the timestamp (see the plugin README).
• Checkout errors: gateway checkout failures are shown with customer-safe text and the gateway requestId when present. Unresolved disputes use CHECKOUT_BLOCKED_BY_DISPUTE; final merchant-loss Customer Risk Holds use CHECKOUT_BLOCKED_BY_CUSTOMER_HOLD or CHECKOUT_RESTRICTED_BY_CUSTOMER_HOLD when only safe bank-transfer methods are allowed.
• Troubleshooting logs: aMember error logging records safe gateway metadata for support, including request ID and dispute/customer-risk-hold identifiers, instead of full checkout request bodies.

Related docs

• Server integration checklist — Same hostname and webhook rules for custom backends
• Sites & Domains — Site ID and IPN URL on each site
• API Keys — creating keys with the scopes your integration needs (official plugins use checkout:create)
• Webhooks & IPN — outbound IPN format and signature algorithm