Paga Business
Keep Paga Business in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
12 ways to read.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- 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.
Connected, approved, proven.
The things teams do most with Paga Business, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Get business account balanceRead
Example flow
- Paga Business · Get business account balanceDone
- 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 Paga Business.
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 Paga Business
- Paga Business'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 your own account when you are ready to go live.
For developers
Technical detail
Read the Paga business balance, transaction history with fees, operation status, Paga Collect history and payment-request status (with refund status), and catalogues without moving money.
Paga API docs- Source actions
- 12
- Data types
- 12
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.
Balance1
- Get business account balanceSource
Read the integrating business's Paga balance; POST is a balance inquiry, with no financial write.
Banks1
- Bank list inquirySource
Banks available on the Paga platform with their UUIDs.
Collect history1
- Collect payment historySourceIncremental
Paga Collect activity in a UTC date-time window: payment requests and persistent payment accounts with their amounts and statuses. Optionally narrowed to one payment request or account reference.
Collect status1
- Get Collect payment request statusSource
Amount requested, amount paid and refund status of a Paga Collect payment request (or persistent account operation), by its reference.
Data bundles1
- Data bundle inquirySource
Data bundles and prices for one mobile operator (catalogue only; nothing is purchased).
Merchant services1
- Merchant services inquirySource
Services and prices offered by one merchant.
Merchants1
- Merchant list inquirySource
Registered merchants (billers) on the Paga platform.
Mobile operators1
- Mobile operator inquirySource
Mobile operators on the Paga platform (catalogue only; nothing is purchased).
Operation status1
- Get operation statusSource
Status, fee and transaction ID of a previous operation by its reference number.
Recent transactions1
- Recent transaction history inquirySource
The last five transactions on the business's own Paga account.
Transaction status1
- Get transaction statusSource
Status, amount and type of a transaction executed in the last 48 hours, by the merchant reference used for it.
Transactions1
- Transaction history inquirySourceIncremental
Transactions on the business's own Paga account in a date-time window (start inclusive, end exclusive).
Access and limits
- Authentication
- Paga Business principal, credential and hash key
- Plans and access
- Paga Business account with Business REST credentials. This connector queries only the integrating business's own account. Customer principals, credentials and other funding sources are not accepted.
- Test environment
- Obtain the Business REST test endpoint and credentials from Paga; only the documented production origin is registered here. No Nexra provider validation recorded.
- Rate limits
- Provider contract quotas apply; HTTP 429 uses bounded retries and Retry-After when supplied.
- Pagination
- Every inquiry returns one response; transaction history is limited by Paga to the most recent 10,000 results and by Nexra to 2,000 per call (the same cap applies to Collect history).
- Provider events
- Paga sends deposit-to-bank notifications; Nexra does not receive them. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Inquiries only: Nexra never transfers money, deposits to banks, buys airtime or data, pays merchants, dispenses cash or registers customers through Paga.
- Intentionally excluded: moneyTransfer, moneyTransferBulk, validateMoneyTransfer, depositToBank, validateDepositToBank (sends bank account numbers), airtimePurchase, merchantPayment, getMerchantAccountDetails (customer account lookup), dispenseCash, onboardMerchant, registerCustomer and the customer KYC methods.
- Paga Collect: only the history and status inquiries are used. Payment requests, refunds (/refund, /refund/v2), persistent payment account registration, updates and deletion are excluded, and getPersistentPaymentAccount is not used because it returns customer names, phone numbers, identification numbers and bank account numbers.
- Payouts and settlements: Paga has no settlement or payout API. Collected funds land in the Paga business account; withdrawals to a bank appear as transactions in transaction history (transactions.list), and settlement reports are only in the Paga Business portal.
- Fees: Paga has no separate fee report API; fee and tax are fields on each transaction in transactions.list, and on transaction_status.get and operation_status.get.
- Refunds: Paga has no refund list API. The refund status of a Collect payment request is on collect_status.get (refundStatus); refunds made from the business account appear in transaction history.
- Disputes and chargebacks: Paga publishes no dispute or chargeback API; disputes are handled through Paga Business support.
- Collect history: Paga's documentation gives both a one-month and a three-month maximum window; keep windows to one month.
- Inquiries are POST requests with a fresh referenceNumber; Paga does not record them as financial operations. Status inquiries send the original operation's reference instead.
- Transaction history accepts a date-time window (blank start and end read the last 30 days); Nexra refuses a response above 2,000 items, so narrow the window for busy accounts.
- Only the published production origin is supported; a provider-approved sandbox origin must be verified before addition.
Developer reference
- Create the Paga credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Paga Business, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/paga and the Connections API.