Go-live checklist
Run through this on https://test.unipay.co.zw, then send the results to your Axis Solutions contact to request production credentials.
If the Axis Sync Engine integrates for you, your Axis contact runs these checks with you.
Authentication
Section titled “Authentication”- A token request with scope
unipay:bills unipay:paymentsreturns200. - Your system requests about one token per 30 minutes per process, and gets a new one on
401. - The client secret is in a secrets vault, not in code or configuration files.
Publishing bills
Section titled “Publishing bills”- A new bill returns
Created; publishing it again unchanged returnsAlreadyExists. - Changing a bill’s amount and publishing again returns
Updated. - A bill number with a dash or space is rejected — your system strips separators before publishing.
- Accounts with zero and credit balances get bills too (
amount0or negative). - A processor on the test environment can find your bill by number and by account.
Account balances and rates
Section titled “Account balances and rates”If you publish them:
- A snapshot published in chunks, then finalized, makes an account lookup show your balance as
amountDueNow. - An account left out of the next snapshot looks up as status
3(Unknown) after finalizing. - Each snapshot uses a higher
syncGenerationthan the last, and the same one on every chunk. - Your rates, including your base currency at
1, appear inGET currency-ratesfor each day.
Collecting payments
Section titled “Collecting payments”- The first read, without
afterId, returns the test payments made against your bills. - Your checkpoint survives a restart: the next read returns only newer payments.
- Killing your process between storing a payment and storing its
idleads to one stored payment, not two. - A payment with
allocatedAmount: nulllands in your exceptions process, not in an account. - A reversal from the reversals feed is applied to the right payment.
Operations
Section titled “Operations”- You log each call with a timestamp and your
client_id, with tokens and secrets redacted. - You alert if the feed hasn’t been read successfully for longer than you’d accept.
- Separate credentials are ready for production; none are shared with test.
UniPay API v1 · build e1eb5c49 · Powered by Axis Solutions