Skip to main content
For the Open Banking / GBP bank transfer iFrame flow, payment confirmation is delivered via a server-to-server webhook from PCX to your registered endpoint. This is the authoritative completion signal — not a browser redirect.

Webhook-based confirmation

When the payer authorises the bank transfer in their banking app, PCX receives confirmation and immediately fires a webhook to your registered endpoint.

Webhook payload

Webhook payload fields

For webhook setup, security verification, and retry behaviour, see Webhooks.

Confirming payment status via the API

After receiving a webhook, confirm the payment status by querying the PCX API directly from your server:
Or by your own client reference:
Always verify server-side before fulfilling an order. The payment_id is returned in the payment initiation response.

Why webhooks and not a browser redirect

The iFrame payment flow uses Open Banking, where the payer authorises the payment inside their banking app — outside the browser tab containing the iFrame. There is no browser-level redirect back to a partner URL after completion. PCX confirms the payment via a server-to-server webhook that is delivered independently of the payer’s browser session.
Do not attempt to fulfil orders based on the iFrame UI state alone. A webhook payment.completed event from PCX is the reliable fulfilment signal.