Checkout

Return URLs

You can set default return URLs on a profile and optionally override them per payment.


Precedence

  1. Per-payment success_url / fail_url on initiate (HTTPS required when set)
  2. Profile-level success/fail URLs
  3. Platform fallback result page

Query parameters typically include track_id and a status indicator when VenPays redirects the browser.


Native iOS

success_url / fail_url do not control native iOS navigation. The Apple Pay sheet completes in-process. See Apple Pay iOS SDK.

Flutter

The Flutter checkout SDK detects completion by:

  1. Matching the same HTTPS success/failure URLs VenPays redirects to (pass those into VenPaysCheckout.start), and
  2. Polling GET /v1/sdk/checkout/{track_id}/status so the sheet can dismiss even when return URLs differ

If the shopper closes the sheet while still pending, the SDK also calls POST /v1/sdk/checkout/{track_id}/cancel so merchant status becomes cancelled.

Custom schemes (myapp://…) are not supported.

Fulfillment

Browser return URLs are a UX convenience. Always confirm payment state server-side.