amount values in the smallest denomination of the currency (minor unit).
Use this rule:
amount_to_send = major_amount * 100
Example: 100.50 NGN becomes 10050.
Why This Format?
Precision
Prevents floating-point rounding issues in financial calculations.
Consistency
Same amount format across collections, disbursements, and wallets.
Provider Alignment
Matches how payment providers process transaction values internally.
Quick Conversion Table
API Examples
The examples below show the same rule in real requests:1250.75 NGNis sent as125075(amountin kobo)10000.00 NGNis sent as1000000(amountin kobo)
Common Mistakes
Sending decimal amounts
Sending decimal amounts
- Incorrect:
"amount": 1250.75 - Correct:
"amount": 125075
Mixing major and minor units
Mixing major and minor units
Do not send some requests in major units and others in minor units. Standardize conversion in one shared utility.
Converting on frontend only
Converting on frontend only
Conversion logic should run on your backend so it stays controlled and consistent.
Recommended Implementation Pattern
1
Store business amounts as decimals or strings in your app
Keep your display and business logic readable (for example
1250.75).2
Convert right before API request
Convert to minor unit integer (
125075) at your service boundary.3
Log both values for debugging
Log
displayAmount and apiAmount so reconciliation is easier.Related Docs
Authorization
Add required auth headers to your requests.
Wallets
Understand wallet balances and wallet states.
API Reference
Explore request/response schemas.