Skip to main content

Checkout

Checkout is Pago46's web application designed to be embedded as an iframe in your user experience. Users can complete pay-in and pay-out flows with an interface optimized for mobile and desktop.

Why Checkout matters​

Checkout standardizes the final user journey in one place, regardless of the operation type or entry channel. This helps you:

  • reduce implementation time for new flows,
  • keep a consistent UX across web and mobile,
  • accelerate end-to-end testing,
  • simplify operational support with a shared execution path.

Checkout also includes internal capabilities for technical monitoring, error and performance tracking, and operational support. It may load third-party services to improve the user experience, including geospatial components with real-time connections.

Environments​

EnvironmentBase URL
Sandboxhttps://checkout.dev.pago46.io
Productionhttps://checkout.prd.pago46.io

Per-order format:

  • Sandbox: https://checkout.dev.pago46.io/{UUID}
  • Production: https://checkout.prd.pago46.io/{UUID}

You can also open the base URL (without UUID) and manually enter the order id.

redirect_url is returned in order create/retrieve responses and points directly to the Checkout URL for that specific order.

Iframe integration​

Recommended flow:

  1. Create the order in Pago46.
  2. Take redirect_url from the order response.
  3. Load that redirect_url in an iframe inside your app.
  4. For QA, also validate manual UUID input from the Checkout home page.

Base iframe example:

<iframe
  src="https://checkout.dev.pago46.io/01952d91-a0ff-7f57-8f4e-68d95be01122"
  width="100%"
  height="720"
  style="border: 0"
  allow="clipboard-write"
></iframe>

Practical recommendations for web iframe integration:

  • Use full width and enough height to avoid excessive inner scrolling.
  • Do not block cookies, storage, or in-domain navigation for Checkout.
  • Allow clipboard-write and standard browser capabilities when needed.
  • Handle session expiration and reloads without breaking your parent screen.
  • For QA, also test base URL access with manual UUID entry.

Mobile app integration​

Checkout is integrated as a webview, with no additional SDK required.

Mobile app with WebView​

  • Load redirect_url directly in the WebView.
  • Avoid intercepting Checkout navigation unless strictly needed.
  • Keep a stable User-Agent to reduce rendering inconsistencies.

Native app (iOS/Android)​

  • Embed Checkout as a webview in your payout/collection flow.
  • Handle the back action carefully to avoid accidental flow exits.
  • Define clear rules for opening external links outside the WebView.

React Native app​

  • Integrate Checkout via WebView (no proprietary SDK required).
  • Keep the same contract: receive redirect_url and load it in view.
  • Test full foreground/background cycles to validate continuity.

User permissions that may be required​

Depending on the flow and operational context, Checkout may require:

  • approximate or precise location (geospatial services and nearby points),
  • stable internet/network access for real-time updates,
  • browser or WebView permissions related to geolocation.

Recommendation: explain why each permission is needed before system prompts.

  1. Create a sandbox order.
  2. Take redirect_url and load it in iframe or WebView.
  3. Complete the flow with the preloaded order URL.
  4. Repeat from Checkout home and manually enter UUID.
  5. Validate behavior on desktop, Android, and iOS.

Demos​

Android​

iOS​

Desktop​