The developer-first toolkit for building compliant financial products.
/blank/
. If you are new to Blnk or open-source fintech developer tools, this is where you should start.
blnk.json
:
Field | Description | Required | Type |
---|---|---|---|
name | A name that best describes the function of the ledger | Yes | string |
meta_data | Custom data associated with the ledger being created | No | object |
Field | Description | Required | Type |
---|---|---|---|
ledger_id | The unique id of the ledger that this balance belongs to. | Yes | string |
currency | The currency in which transactions recorded in this balance will be recorded. | Yes | string |
meta_data | Custom data associated with the balance being created | No | object |
Field | Description | Required | Type |
---|---|---|---|
amount | The transaction amount. | Yes | float |
reference | Your unique transaction reference to ensure idempotency. | Yes | string |
currency | Short code for your asset class. See also: Asset classes | Yes | string |
precision | Precision for the currency/asset passed. See also: Precision | No | int64 |
source | Sender’s balance ID | Yes | string |
destination | Recipient’s balance ID. | Yes | string |
description | Description or narration of the transaction. | No | string |
meta_data | Custom data associated with the transaction | No | object |
meta_data
object is encouraged; it provides you with 360-degree insights about each transaction record. Examples of data you can pass include sender_name
, account_number
, bank_name
, receiver_name
, payment_id
, ip_address
, location
, payment_method
, etc.