Skip to content

Capabilities · Run & protect

API integration

Connect payF to your own product and systems.

What it does

Automate payouts, collections, conversions and balance management from your own platform. Webhooks keep your systems updated as payment statuses change. Documentation and sandbox access are provided to clients during onboarding.

At a glance

  • Endpoints for payouts, collections, FX and balances
  • Webhooks for real-time status updates
  • Sandbox environment for testing
  • Documentation and integration support at onboarding

Why it matters

  • One API for the whole stack

    Endpoints for payouts, collections, FX and balances, so you build once.

  • Webhooks for status changes

    Your systems are updated in real time as payment statuses change.

  • A sandbox to test in

    Build and test against a sandbox environment before going live.

  • Support while you integrate

    Documentation and integration support are provided during onboarding.

How it works

The typical path, from the first step to money where it needs to be.

  1. Access

    Get sandbox credentials and documentation at onboarding.

  2. Build

    Integrate payouts, collections, FX and balances.

  3. Test

    Run your flows end to end in the sandbox.

  4. Go live

    Switch to production and listen for webhooks.

Illustrative flow. Exact steps, methods and timings depend on the corridor and are confirmed at onboarding.

Questions, answered

Something else on your mind? Ask us directly.

Is there a sandbox?

Yes. A sandbox environment is provided for testing during onboarding.

Where is the documentation?

Documentation and sandbox access are provided to clients during onboarding.

How do we know when a payment status changes?

Webhooks keep your systems updated as payment statuses change.

Talk to people who move money every second

Book a call