Skip to main content
POST
Credit a subscriber’s wallet. Partner routes use HMAC headers, so this page provides a copyable request instead of the interactive playground.

Authentication

string
required
API key ID issued for the partner integration
string
required
Partner identifier such as VULT
string
required
RFC3339 timestamp used when generating the signature
string
required
Hex-encoded HMAC-SHA256 of METHOD + "\n" + PATH + "\n" + TIMESTAMP + "\n" + BODY

Request Body

string
Subscriber phone number
string
Subscriber card serial
integer
required
Amount in cents (for example 50000 = 500.00)
string
required
Partner’s unique transaction reference
Provide either phone_number or card_serial

Example

Response

Transaction Flow

  1. Partner account is debited (may go negative - clearing account)
  2. Subscriber account is credited
  3. Transaction and ledger entries are created
  4. Generates unique transaction ID

Errors

Authorizations

Authorization
string
header
required

API Key for third-party integrations (WhatsApp, Smart PAY, VULT). Format: 'Bearer olive_live_xxxxxxxxxxxxx'

Headers

X-API-Key-ID
string
required
X-Partner-ID
string
required
X-Timestamp
string
required
X-Signature
string
required

Body

application/json
amount
integer
required
reference
string
required
phone_number
string
card_serial
string

Response

200 - application/json

Success

The response is of type object.