Everything between your checkout and your providers.

Connect the providers you already use, decide where each payment goes, and see every payment through to the end. One API, one dashboard.

  • PaystackCard, bank transfer, USSD, bank account, mobile money (GHS, KES)
  • FlutterwaveCard, bank transfer, USSD, bank account, mobile money (GHS, KES)
  • FincraBank transfer, and mobile money across seven currencies

Take a payment, whoever runs it.

The same request and the same answer for every provider, and a final status you can trust.

  1. 01

    One API for every provider

    Send one request to /collections. Tunnel picks the provider, starts the payment and gives you a single response shape back, whichever provider ran it.
  2. 02

    Hosted or direct

    Redirect the customer to the provider’s page, or complete bank transfers, USSD and mobile money inside your own checkout with the direct flow.
  3. 03

    Payments settle without webhooks

    Tunnel asks the provider for the final status itself, every few seconds while a payment is fresh. You never have to set up provider webhooks.
  4. 04

    Underpayments are caught

    If the customer sends less than they were asked for, the payment is marked failed with the reason, in the dashboard and in your webhook.

Decide where each payment goes.

Routing rules live in the dashboard. Change them without a deploy, and see exactly why a payment went where it did.

  1. 01

    Rules you can read

    Route by currency, method and amount. “NGN bank transfers go to Paystack” is a rule, written in a form, not in code.
  2. 02

    The most specific rule wins

    A rule that matches on more conditions beats a broader one. Ties go to the higher priority. Everything else goes to your first connected provider.
  3. 03

    Conflicts are refused

    Two rules that would send the same payment to different providers cannot both be saved. You see which rule clashes and why.
  4. 04

    Try a payment before it is real

    Describe a payment and the Rules page shows which rule takes it, which ones it skipped and the reason for each.
  5. 05

    Pause, do not delete

    Switch a rule off while a provider has a bad day. Changes reach live traffic within 60 seconds.
  6. 06

    Failover on hosted payments

    When a provider refuses a hosted payment, Tunnel can retry it on your next provider before your customer sees an error.

Built for the people who run it.

For the developer who integrates once, and for the team that answers when a customer asks where their money went.

  1. 01

    Payment links

    Share a link and get paid by bank transfer, USSD or mobile money, with no website. Fixed or open amounts, an expiry and a redirect when it is done.
  2. 02

    Signed webhooks with retries

    Every event carries a stable event ID and a signature. Failed deliveries are retried six times over about nine hours, then marked failed.
  3. 03

    Test and live, kept apart

    Separate keys, providers, links and payments for each mode. Test mode never moves real money.
  4. 04

    Keys locked to your domains

    API keys can be limited to the domains you list, and every change in the workspace lands in the audit log.

See it running before you sign up.

The demo workspace has providers, rules, payments and webhooks already in it. No account needed.