Pay Bill Batch
pay_bill_batchPay airtime or data to multiple recipients in ONE call — the same multi-recipient batch Telegram/WhatsApp/X support ("send 500 to X and 1000 to Y"). One PIN authorizes the whole batch. Recipients are grouped by (chain, token); each group's capacity (balance + approved agent limit) is checked against that group's own subtotal — but if ANY group is short, the ENTIRE batch is refused before anything moves (all-or-nothing on capacity; paying 6 of 8 recipients because the 7th was under-funded is worse than one clear error up front). Once capacity clears, recipients are paid one at a time and the response reports each individually, since a single vend failure partway through must not be reported as if the whole batch failed. AIRTIME and DATA only — electricity, cable, education, and international are not batchable; call pay_bill for those, one at a time. For DATA, call list_plans first and give each recipient needing one its own real variation_code. EXECUTES IMMEDIATELY: no delay/schedule option, same as pay_bill — for a delayed/recurring batch, call schedule_bill once per recipient instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pin | Yes | 4-6 digit PIN set when the API key was created. Required once for the whole batch. | |
| chain | No | Default chain for recipients that don't set their own. Falls back to the chain approved when the API key was created. | |
| token | No | Default token for recipients that don't set their own. Falls back to the token approved when the API key was created. | |
| api_key | No | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. | |
| recipients | Yes | At least 2 recipients (a single recipient should just use pay_bill), at most 20 per call — split a larger batch across several calls. | |
| customer_email | No | Optional — used for receipts if known, applies to the whole batch. |