Skip to content
Start in the sandbox
All connectors
Interswitch · Quickteller logo

Interswitch · Quickteller

Accounting, billing & payments

Keep Interswitch · Quickteller in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

11 ways to read, 1 way to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Interswitch · Quickteller with Nexra

Connected, approved, proven.

The things teams do most with Interswitch · Quickteller, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Send a payoutpayouts.createApproval by rule
  • List bank codesbanks.listRead

Example flow

  1. Interswitch · Quickteller · List bank codesbanks.listDone
  2. Interswitch · Quickteller · Send a payoutpayouts.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Interswitch · Quickteller.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Interswitch · Quickteller
  • Interswitch · Quickteller's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect a Interswitch · Quickteller test account before you go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Nigeria: Quickteller v5 bills and status, Web Checkout status, (Test only) Quickteller Business transactions and refunds, and governed bank payouts from your Quickteller Business wallet.

Interswitch · Quickteller API docs
Source actions
11
Destination actions
1
Data types
10

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

banks1
  • List bank codesSource

    Banks with their CBN and Interswitch codes.

biller payment items1
  • List biller payment itemsSource

    Payment items (and their payment codes and amounts) for one biller.

billers1
  • List billersSource

    Billers available to the terminal, optionally for one category.

categories1
  • List bill categoriesSource

    Read the Quickteller bill-payment categories without paying a bill.

checkout transactions1
  • Read Web Checkout transaction statusSource

    Confirm the status of a Web Checkout (inline or redirect) payment by your transaction reference. Supply the merchant code and amount for the v1 status query, or leave them out to use v2, which reads the merchant from the token.

gateway transactions1
  • List Quickteller Business transactionsSourceIncremental

    Quickteller Business (Payment Gateway) payments in a date range with amount, remittance amount, settlement and remittance status.

payout banks1
  • List payout banksSource

    Banks and other institutions a payout can be sent to, with the code to use as the recipient bank.

payouts2
  • Send a payoutDestinationNot retried automaticallyApproval before production

    Pays a Nigerian bank account from your prefunded Quickteller Business wallet. Moves money: it runs only when you enable it on your own connection, under any approval rules and limits you set.

  • Get payout statusSource

    Whether a wallet payout is processing, successful or failed, with its fee, by your transaction reference. Use it to confirm a payout before booking it, and to settle a payout whose outcome is uncertain.

refunds2
  • Get Quickteller Business refundSource

    One refund by its refund reference.

  • List Quickteller Business refundsSourceIncremental

    Refunds already made on Quickteller Business payments, by merchant and date.

transactions1
  • Read bill-payment statusSource

    Query an existing merchant request reference without submitting a payment.

Access and limits

Authentication
Authorised Interswitch bearer token and TerminalID; optional payout keys
Plans and access
An Interswitch Quickteller Service v5 integration with a terminal ID and client credentials. Bill-payment access is enabled per terminal by Interswitch; production access follows their go-live process.
Test environment
QA at qa.interswitchng.com with Interswitch's published test terminal and credentials. Payouts test on payouts-sandbox.interswitchng.com with your Quickteller Business test client ID, secret and wallet (test account 0037320662 at bank TRP succeeds).
Rate limits
Interswitch does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries.
Pagination
Quickteller v5 catalogue reads return one page; Quickteller Business transactions and refunds page with pageNum and pageSize.
Provider events
Interswitch sends payment notifications to the webhook configured for the merchant. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Quickteller v5 bill catalogue and transaction-status reads, plus Web Checkout status by reference. Card acquiring, Verve and the rest of the Payment Gateway are separate APIs on other hosts and products.
  • Test connections only: Quickteller Business transactions (GET /paymentgateway/api/v1/transactions, documented only on sandbox.interswitchng.com) and refunds (GET /paymentgateway/api/v1/refunds, documented only on qa.interswitchng.com). Interswitch publishes no production host for either, so on a Production connection these reads stop with a clear message before any call.
  • Fees: Interswitch reports no fee amount through an API. Quickteller Business transactions carry the remittance amount (what is paid to you after charges), surcharge and fee type.
  • Settlements: Interswitch has no settlement API; the settlement and split settlement reports are viewed and exported in the Quickteller Business dashboard (upload the export to a reconciliation). Quickteller Business transactions carry settlementStatus, remittanceStatus and the remittance amount.
  • Money movement is customer-governed: payouts (Send a payout, from your prefunded Quickteller Business wallet to a Nigerian bank account) run once you enable them on your own connection, with any approval rules and limits you set. Payments asked for by an AI wait for a person to approve them.
  • Payouts are keyed by your transaction reference. Interswitch documents no duplicate check, so a payout is sent once and an uncertain one is held for a person, who reads it with Get payout status; Nexra never resends it. A FAILED payout is final and Interswitch reverses the wallet debit.
  • Payouts are read one at a time by reference: Interswitch has no list of single payouts, so reconciliation looks up the references on your ledger's unmatched entries. Batch payouts and push-to-card payouts are not offered.
  • Disputes and chargebacks: Interswitch publishes no dispute or chargeback API for merchants; the Transaction Search API that shows dispute status is gated (see below).
  • Gated, so not implemented: Transaction Search (quick search, reference search and transaction details on switch-online-gateway-service.k9.isw.la) needs a separate Developer Console project, ClientId header and go-live approval, and its quick search accepts card numbers; the PayDirect transaction report API (paydirect-service.k8.isw.la) and wallet balance (api-gateway.interswitchng.com) need separate partner onboarding.
  • Webhook configuration has no public API; webhooks are configured in the Quickteller Business dashboard.
  • Intentional exclusions: bill payments (POST /Transactions), customer validation (returns customer names), airtime and e-pin vending, Quickteller v5 funds transfers (Send Money TransferFunds needs the sender's name, phone and e-mail and a per-request MAC; Nexra pays out through the Payouts service instead), batch and push-to-card payouts, paycodes, pay-bill link creation, card purchases and tokenisation, and refund creation (documented only on a test host).
  • For Quickteller v5 and Web Checkout, supply a current Passport token (tokens last about 12 hours); the production Passport host is not published alongside the v5 contract. For payouts, Nexra mints tokens from your client ID and secret at the Passport hosts the payouts guide publishes.
  • Interswitch publishes no payload for payout events, so there is no payout trigger; read the outcome with Get payout status.

Developer reference

  1. Create the Interswitch · Quickteller credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Interswitch · Quickteller, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Interswitch · Quickteller docsAPI referenceInterswitch · Quickteller docsAuthenticationInterswitch · Quickteller docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/interswitch and the Connections API.