AbaPay DOCS & FAQ

Three ways, all running the same payment engine. In this app: pick the service, enter the number, confirm, and sign in your wallet. By chat: message AbaPay on Telegram, WhatsApp or X in plain language — "send ₦500 airtime to 08012345678". Through an AI assistant: connect AbaPay as a tool over MCP and just ask it to pay.

Chat and AI payments need a spending allowance approved first (or they'll send you a signed link to pay yourself, one time).

Yes — add the bot to a group and tag it (@AbaPayAgentBot) to use it there. Anything sensitive (balances, receipts, PINs) is always sent to you privately, never posted where the group can see it.

One group-only trick: ask it to pick a few phone numbers that were posted in the chat recently and recharge them — e.g. "recharge 5 random numbers from the last 30 minutes, 200 each", or the same with data instead of airtime. It confirms the total and asks for your PIN by DM first, then posts the result (numbers, amounts, proof) back in the group once it's done. Electricity and cable aren't included in this — there's no safe way to tell a meter or smartcard number apart from any other number someone posts, so those still need you to name the account directly.

Some wallets — Zerion and a few others — show a risk warning on AbaPay's payment signature. The warning is about the shape of the request, not about AbaPay.

AbaPay settles payments using x402, an open payment standard. It asks you to sign a one-off permission for a single, exact amount to be collected for the bill you're paying. Automated scanners can't tell that kind of permission apart from the one a scam site would ask for, so some of them flag every request of that shape.

Check the wallet screen itself, which is the part that can't lie to you: it shows the exact amount and the recipient. The amount should match your bill, and the recipient should be AbaPay's payment contract. If those look right, the request is genuine. If they don't, cancel — and please tell us.

Cancelling is always safe. Nothing is charged, and nothing is left half-done.

When your wallet is a separate app rather than one built into this browser, AbaPay sends the approval request to it — but nothing can force that app to open on top of what you're doing. The request is sitting in your wallet waiting for you.

Switch to your wallet app and approve it there, then come back. AbaPay says so on screen rather than leaving you watching a spinner.

If no prompt arrives at all, the connection to your wallet has usually gone stale. AbaPay reconnects you automatically when you return, and that remembered connection can look fine — your address and balance show — while the link to your wallet is actually closed, so requests reach nothing. AbaPay now checks that link before asking you to approve anything, and tells you to tap Connect again if it has dropped.

If a request still goes unanswered, AbaPay stops waiting after ninety seconds rather than spinning forever, and switches to its standard payment route — which will ask you to approve again, in your wallet app. That second request is the real one: the first was abandoned, so approving it late now does nothing and cannot charge you twice.

No — don't pay again. That message means AbaPay checked the blockchain itself and found that your payment really did leave your wallet, even though the payment service that handled it reported an error instead of a receipt.

AbaPay deliberately stops there rather than offering to retry. A retry in that situation would be a genuine second payment for the same bill, and the whole point of the check is to make sure that can't happen to you.

Your payment is flagged for us to reconcile by hand. Check your History tab — if the bill hasn't been delivered or refunded shortly after, contact support and we'll trace it from the payment itself.

It's a proof that the wallet is yours, and it is safe: signing it moves no money, approves no payment, and grants no spending permission. The message says exactly that — read it in your wallet and you'll see.

Here's why it's needed. Your wallet address is public information. Without a signature, anything that simply claimed your address could ask AbaPay to show that address's payment history — the numbers you've recharged, the meters you've paid, the amounts. A signature can only be produced by whoever actually holds the wallet, so it turns "this address was claimed" into "this address was proven".

You're asked once per browsing session, not per page. If you decline, you're disconnected — nothing breaks, and you can tap Connect and approve it whenever you like.

If your wallet can't produce that kind of signature at all, you stay connected and can still pay as normal; only your history stays hidden, because that's the part that needs proof.

Both live in the same place: tap the network badge at the top of the app — the small pill showing BASE or CELO. It opens a short menu with the networks you can switch to and a Disconnect option.

The badge used to just flip to the other network the moment you touched it, which made a mis-tap awkward to undo. Now nothing happens until you actually choose something, and the menu closes as soon as you do.

Disconnecting doesn't touch your money — it only ends this app's connection to your wallet. Your funds never left it in the first place. Tap Connect whenever you want to pay again.

Open Agent Hub, pick that channel, and use the Open button shown there. It takes you straight to the bot.

You don't need to link again — your account is still connected. This is just a shortcut back to the conversation, which matters if you changed phone or cleared your chats.

Because connecting your wallet should be your decision, not ours. AbaPay no longer restores a connection on its own when you open or refresh the page — you tap Connect, and you choose which wallet to use.

Connecting by itself caused two real problems. It picked a wallet on your behalf when you had more than one, and it hid the chooser — including the WalletConnect option for phone wallets — behind a button there was no reason to press. It could also restore a connection that looked fine but had quietly gone dead, so payments vanished with no prompt and no error.

There are three exceptions, where AbaPay is running inside your wallet and there is only one account it could possibly mean: MiniPay, Base App and Farcaster. Those still connect automatically.

The trade is that refreshing the page means tapping Connect again. Nothing is lost when you do — your money never leaves your own wallet either way.

That's deliberate. Inside Valora's built-in browser, AbaPay used to appear connected by itself — and then payments got stuck: an approval prompt would come up, you'd tap Allow, Valora would say the connection succeeded, and the payment would keep loading with no second prompt ever arriving.

Valora connects properly over WalletConnect, so that is the only route AbaPay now uses there. Tap Connect and choose Valora — it's the same app you're already in, so it takes one tap — and payments go through normally after that.

Valora works on Celo. If AbaPay is showing Base when you connect, it switches itself to Celo to match your wallet; pick a Celo token (USDC, USD₮ or USAT) and pay as usual.

MiniPay (Opera Mini's Celo wallet), Valora, MetaMask, Coinbase Smart Wallet / Base Account, and any other wallet reachable over WalletConnect or injected into your browser. AbaPay also runs as a Farcaster Mini App. Valora connects over WalletConnect — tap Connect and pick it — which is the only route it handles reliably.

Wallets that support smart-account gas sponsorship on Base get it automatically — the app detects the capability and batches the token approval and the payment into one sponsored transaction. Every other wallet just pays normal network fees, with no difference in behaviour.

Open AbaPay inside MiniPay and it locks to Celo; inside Base App or Farcaster and it locks to Base — there's only ever one chain either wallet can pay on, so the network switcher, balances and token list all show that one chain, with an Exit button to disconnect. Everywhere else — an ordinary browser, any WalletConnect wallet — both chains stay available and switchable.

If you have a wallet installed in this browser, AbaPay uses it directly — it opens that wallet's own approval window, and if several are installed it asks which one you want. No QR code, no third-party service involved.

WalletConnect is only used when there is no wallet in the browser at all. That is where this usually goes wrong: connecting that way goes through a background service that some networks block, and because it's a WebSocket it fails silently instead of showing an error.

Open the network check and it will tell you in a few seconds whether something is being blocked, and exactly what.

The quickest fix is to open AbaPay inside MiniPay, Base App or Farcaster — they connect your wallet directly and need none of the blocked services. Switching to a different network (mobile data instead of Wi-Fi, or the other way round) or turning on a VPN also works.

Base and Celo — those two, plus their public test networks, and nothing else. Base is the default: it's what AbaPay connects to unless your wallet puts you somewhere else, and you can switch to Celo at any time. USD₮ and USDC work on both chains; USAT is Celo-only.

The token picker filters itself to whatever chain your wallet is on, so you can't accidentally choose one that doesn't exist there. On Base it offers USDC first, then USD₮; on Celo, USD₮ first. Sending funds to our contract by hand, on another network or in another token, is not a payment and can't be matched to an order.

The blockchain part confirms in roughly a few seconds on both Celo and Base. Utility delivery normally follows immediately after confirmation — electricity tokens and education PINs appear on the receipt itself. If a provider is slow, the transaction sits in a PENDING state and our webhook keeps chasing it rather than declaring failure.

No. There's no AbaPay balance to top up, and we never hold your keys. Your stablecoins stay in your own wallet until the moment you pay a bill, and they go straight into the payment smart contract. We can't move your funds without either your signature or an allowance you explicitly approved on-chain.

Yes, and they're always shown in the total before you confirm. There's a small flat platform fee on electricity, cable TV, education and bank transfers. Airtime, mobile data and international top-ups carry no platform fee at all.

Blockchain gas is separate, goes to the network rather than to us, and depends on your wallet and chain — Base smart wallets are often sponsored, so free.

Airtime, mobile data (including SME bundles), electricity (prepaid and postpaid), cable TV (DStv, GOtv, Startimes), education PINs, bank transfers, and international airtime/data.

The providers inside each category are pulled live from our payment providers, so the list only ever shows what can genuinely be bought right now. If a provider disappears from the picker, it isn't purchasable at that moment — which is deliberately better than letting you pay for it and fail afterwards.

Type the destination account number — we check it against every Nigerian bank automatically and tell you whose account it is, so you don't need to know or select the bank yourself. If more than one bank has an account under that exact number, we show you the short list of matches so you can confirm which one is yours.

Once confirmed, the transfer settles in real time as an actual bank payout, not a top-up voucher.

Not right now, honestly. WAEC result-checker and WAEC registration PINs work — in the app, in chat, and through a connected AI agent. JAMB is fully built on our side, but it isn't enabled on our current merchant account with our payment provider, so it doesn't appear in the live product list and can't be bought.

If that changes at their end it will simply start appearing, with no update needed from us.

Every country our payment provider currently covers — including Ghana, Kenya, South Africa, the UK and the US. We deliberately don't publish a count, because we read that list live from the provider rather than keeping our own copy of it, so it can change without us knowing.

Pick the country in the app (or just name it in chat) and you'll see its own operators, plans and local currency. If a country isn't in the live list, the agent will tell you so instead of promising something that would fail at delivery.

Yes — just say so in chat: "every Tuesday buy ₦200 MTN airtime", "pay my meter on the 28th every month", or a one-off "top up 08012345678 in an hour". Ask to "show my schedules" or "cancel my airtime schedule" the same way.

Automatic execution is opt-in per schedule; by default a schedule only reminds you. When it is on, it's still bounded by your on-chain allowance and our per-transaction and daily caps, runs at most once per due date, and pauses itself after repeated failures.

The outcome is reported back on whatever channel you created the schedule from. On WhatsApp there's a wrinkle outside AbaPay's control: WhatsApp only lets a business send you a free-form message within 24 hours of your last one, so a schedule due days later is delivered as a formatted notification instead. Either way, the full receipt is always in your History tab.

On the receipt, immediately after a successful payment — shown in full, and shareable as an image or saveable as a PNG/PDF. It's also in your History tab, and sent by email where we have your address.

In the app, you sign every payment in your wallet — nothing moves without that signature. With an agent, you approve an on-chain spending allowance once from the Agent Hub, for one specific chain and one specific stablecoin. After that the agent can pay without a fresh signature each time, but only up to what's left of that allowance.

The cap is enforced by the smart contract itself, not by our servers, so it cannot reach the rest of your wallet no matter what goes wrong on our side. Our own per-transaction and daily limits sit on top of yours.

Open the Agent Hub tab, pick the chain and stablecoin you want the agent to be able to use, and approve a limit — that's an on-chain transaction only you can sign. To revoke, set the limit back to zero; it takes effect on-chain immediately. Note that unlinking a chat account stops that channel but does not by itself zero your allowance, so do both if you want a full stop.

MCP (Model Context Protocol) is the standard that lets an AI assistant like Claude use AbaPay as a tool. A connected assistant can describe what AbaPay supports, list real purchasable plans with real prices, read your balance and remaining allowance, and — with your PIN — pay a bill.

It reaches exactly the same engine as chat: same on-chain allowance ceiling, same PIN gate with lockout, same kill switches, same operator caps, same spend alerts. It is not a looser door.

OAuth if your client supports it: you authorize once in the browser and the connection is remembered, so there's no credential to paste into every new conversation. The API key you create in Agent Hub → MCP is the fallback for clients that can't do the OAuth flow.

Both can be revoked instantly from the Agent Hub, and revoking kills every token issued against that link. An expired or revoked authorization makes the assistant ask you to reconnect rather than quietly failing.

Yes — every single payment, every time. Authorizing the connector means 'this assistant may act for me'; it never means 'this assistant may spend'. Without the PIN a connected assistant can only read your balance and the plan catalogue. If something claims it can pay without asking for your PIN, treat that as a red flag.

No, and it's important not to confuse them. Your wallet password and recovery phrase belong to your wallet app and we never see them. Your AbaPay PIN is a separate 4–6 digit code you set when linking a chat account or creating an MCP credential.

It gates one thing: authorising a payment through those channels. It can't move funds on its own — it only unlocks spending inside the allowance you already approved on-chain. Repeated wrong PINs lock the channel out.

It can't, for the services where that would matter. Data bundles, cable packages and education products all require a real plan code, and the connector exposes a list_plans tool that returns the actual purchasable plans, codes and current prices from our payment provider. If an agent can't get a real code, the payment is refused before any money moves rather than settling on-chain and failing at delivery.

It checks first. If there's no allowance for that chain and token, it says so and gives you the choice — approve a limit now in the Agent Hub, or complete just that one payment via a secure signed link. If another stablecoin on the same chain already has both the balance and the approved limit to cover it, it will tell you that too, so you can just use that one instead.

Yes — Telegram, WhatsApp and X can be linked independently to the same wallet, alongside one or more MCP credentials, and each can be managed or unlinked separately from the Agent Hub.

No, and that's deliberate. Bank transfers move money to a third party, so they must be confirmed with your own wallet signature in the app. The agent will refuse and point you there rather than spending from an allowance.