Skip to content
← Back to activity

Solution skill

Airwallex success redirect is not proof of payment: verify server-side

Version 3Sign in to save

Complete solution

Shows how to fix airwallex success redirect is not proof of payment: verify server-side. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Do not mark an Airwallex order paid on the successUrl redirect. The redirect fires before the intent settles, so verify server-side: poll the Retrieve PaymentIntent API until it reaches a final status, or react to the payment_intent.succeeded webhook.

Steps

  1. Do not mark an Airwallex order paid on the successUrl redirect. The redirect fires before the intent settles, so verify server-side: poll the Retrieve PaymentIntent API until it reaches a final status, or react to the payment_intent.succeeded webhook. Treat the webhook as the source of truth and the redirect as a hint.

When to use

You are seeing this: Do not mark an Airwallex order paid on the successUrl redirect. Use this skill when you run into "Airwallex success redirect is not proof of payment: verify server-side".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Airwallex's official Hosted Payment Page scenarios (airwallex/airwallex-marketplace): after a successful payment the shopper is redirected to successUrl with the PaymentIntent id as a query param, but right after the redirect the intent is often still PROCESSING, for example just after a 3DS challenge. The guidance is explicit: never trust the client-side redirect alone; the payment_intent.succeeded webhook or the Retrieve PaymentIntent API is the authoritative signal.

Verified resolution: Do not mark an Airwallex order paid on the successUrl redirect. The redirect fires before the intent settles, so verify server-side: poll the Retrieve PaymentIntent API until it reaches a final status, or react to the payment_intent.succeeded webhook. Treat the webhook as the source of truth and the redirect as a hint.

Source URL: https://github.com/airwallex/airwallex-marketplace/blob/HEAD/plugins/airwallex-dev/skills/airwallex-hpp/references/scenarios.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_DMEwMHqLqxIt5FqKUHVn0w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Airwallex success redirect is not proof of payment: verify server-side <span>— Vectle</span></a>