Use these endpoints to view and manage personal details for a Customer.
Jiko Partner API (Version: fd60d28d)
Welcome to the Jiko API Reference! Jiko enables you to integrate money storage and movement, backed by the safety and security of US Treasury Bills. Use the Partner API if you are building an application that embeds Jiko’s services and offers Jiko products to your own customers. The Partner API will then enable your application to interact with Jiko on behalf of your customers.
At the core of our platform is the Jiko Pocket: a pair consisting of a bank account and a brokerage account. When money is deposited into a Pocket, the funds are automatically invested in T-bills. When a payment or withdrawal is made, T-bills are immediately liquidated and used as cash. Customers can have multiple Pockets, and each Pocket is associated with a single T-bill maturity: 4-week, 13-week, 26-week or 52-week.
The API Reference covers everything you need to build a full application leveraging the Jiko platform:
- Onboarding customers
- Funding Pockets via ACH or Wire
- Viewing and managing Pockets (including monthly statements and trade confirmations)
- Making payments and transfers via ACH, Wire, On-Us (Book) Transfer or Debit Card
When you’re ready to start building, please contact us at partner.support@jiko.io to request sandbox access.
Use these endpoints to view Account information. Jiko Accounts (also known as Pockets) consist of a bank account and a brokerage account. When funds are deposited into a Pocket, they’re immediately invested in T-bills.
In the API interface, the Account object encapsulates both accounts and can be treated as a single account to deposit to or withdraw from.
Use these endpoints to view Transactions of funds moving in and out of Jiko Accounts, specifically the bank account component (cash deposits and withdrawals). For viewing information regarding the brokerage account component (buying and selling of T-bills), use Trades.
Use these endpoints to view Counterparties. Counterparties represent external accounts when moving funds in or out of a Jiko Account. Jiko will only transfer funds between accounts where the Counterparty has status: “VERIFIED”, meaning ownership of the account has been confirmed.
Request
Initiates an On-Us Transfer between two Pockets.
On-Us Transfers can be made in four directions (defined by type):
PARTNER_CUSTOMER_FUNDING: From a Partner’s Pocket to a Customer’s PocketPARTNER_CUSTOMER_DEFUNDING: From a Customer’s Pocket to a Partner’s PocketINTERNAL_REALLOCATION: Between two Pockets belonging to the same CustomerPEER_TO_PEER: From a Customer’s Pockets to Customer’s On-Us Counterparty
On-Us Transfer amounts can be specified two ways (defined by amount.type):
REQUESTED_AMOUNT: Transfer a specified dollar amountFULL_WITHDRAWAL: Transfer the Pocket's total available balance (net of fees).amount.typecannot beFULL_WITHDRAWALwhentypeisPARTNER_CUSTOMER_FUNDING.
On-Us Transfers can be processed asynchronously or synchronously. We strongly recommend processing On-Us Transfers asynchronously (setting async_mode to true). Asynchronous transfers will be created in a PENDING state and status updates will be delivered via Webhooks.
The ID for this transfer, auto-generated if not provided.
The ID for this transfer, auto-generated if not provided.
A description of the transfer, visible on statements.
A description of the transfer, visible on statements.
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Move funds between accounts belonging to the same customer.
Using asynchronous processing is strongly recommended. Status updates will be delivered via Webhooks.
- Production serverhttps://your-partner-name.partner-api.jikoservices.com/api/v1/transfers/on-us/
- Sandbox serverhttps://your-partner-name.sandbox-api.jikoservices.com/api/v1/transfers/on-us/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
- INTERNAL_REALLOCATION
- PARTNER_CUSTOMER_DEFUNDING
- PARTNER_CUSTOMER_FUNDING
- PEER_TO_PEER
curl -i -X POST \
https://your-partner-name.partner-api.jikoservices.com/api/v1/transfers/on-us/ \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'x-jiko-idempotency: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-jiko-signature: string' \
-d '{
"amount": {
"amount_usdc": 10000,
"type": "REQUESTED_AMOUNT"
},
"description": "Moving funds between accounts belonging to the same customer",
"from_account": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"type": "JIKO_ACCOUNT"
},
"to_account": {
"id": "991dd8b5-f103-4158-8c6b-84480cb43652",
"type": "JIKO_ACCOUNT"
},
"transfer_id": "cbb6cfce-f207-45e7-a6b3-1055ab43db51",
"type": "INTERNAL_REALLOCATION"
}'Successful Response
The ID for this transfer, auto-generated if not provided.
The ID for this transfer, auto-generated if not provided.
A description of the transfer, visible on statements.
A description of the transfer, visible on statements.
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
The source of customer funds at the Partner institution.
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "PENDING", "transfer": { "transfer_id": "d4a2d8dd-7def-4545-a062-761683b9aa05", "description": "Disbursing funds from partner to customer", "from_account": { … }, "to_account": { … }, "type": "PARTNER_CUSTOMER_FUNDING", "source": "123456789", "amount": { … } }, "fees": [ { … } ], "object_type": "OnUsTransfer" }
- Production serverhttps://your-partner-name.partner-api.jikoservices.com/api/v1/transfers/on-us/{transfer_id}/
- Sandbox serverhttps://your-partner-name.sandbox-api.jikoservices.com/api/v1/transfers/on-us/{transfer_id}/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://your-partner-name.partner-api.jikoservices.com/api/v1/transfers/on-us/{transfer_id}/' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-jiko-idempotency: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-jiko-signature: string'Successful Response
The ID for this transfer, auto-generated if not provided.
The ID for this transfer, auto-generated if not provided.
A description of the transfer, visible on statements.
A description of the transfer, visible on statements.
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
The source of customer funds at the Partner institution.
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "PENDING", "transfer": { "transfer_id": "d4a2d8dd-7def-4545-a062-761683b9aa05", "description": "Disbursing funds from partner to customer", "from_account": { … }, "to_account": { … }, "type": "PARTNER_CUSTOMER_FUNDING", "source": "123456789", "amount": { … } }, "fees": [ { … } ], "object_type": "OnUsTransfer" }