This section covers the core functionality for managing a pocket. Specifically, it details how to:
Create and modify a pocket.
Retrieve funding instructions for a specific pocket.
Inquire about a pocket's current balance and bank transactions.
Create a new pocket, which automatically establishes both a Jiko bank account and a Jiko brokerage account, with the selected:
Deposit strategy: whether new deposits or incoming third-party payments will be invested in T-bills with a 4-week, or 13-week, 26-week, 52-week maturity *.
Reinvestment strategy: whether matured T-bills must be automatically reinvested in T-bills with a 4-week, 13-week, 26-week, or 52-week maturity *.
With the ability to change the pocket's name, deposit strategy and reinvestment strategy at any time.
* Note: a 1-week strategy is mentioned in the API documentation but cannot be used in the context of your Jiko account.
Important: pockets connected to the JikoNet network operate with a specific 4-week strategy. The Jiko team will partner with you to implement this 4-week deposit and reinvestment strategy when enabling JikoNet for a pocket.
Customer systems:
Collect required account setup information within the customer's organization, such as the name to assign to the new pocket and its deposit strategy (whether received funds must be invested in T-bills maturing in 4, 13, 26, or 52 weeks).
Send to Jiko a pocket creation request, providing the pocket's name, deposit and reinvestment strategies.
Receive from Jiko a confirmation response containing the assigned pocket id.
Retrieve account details (account number, routing information) from Jiko and update the other customer's systems (treasury, payment, accounting...).
| Step | Purpose | Jiko API Endpoints |
|---|---|---|
| 1 | Create a new pocket and receive its Jiko pocket id. | POST /api/v2/pockets/ |
| 2 | Get the list of portals for a given pocket, passing the pocket's id received in the response to the previous step as account_id parameter. Creating a pocket automatically generates a corresponding portal. A portal is the representation of a pocket from the perspective of the outside world: each portal includes its account number and routing number. Multiple portals can be defined for the same pocket. The API response lists portals for the pocket passed as parameter. | GET /api/v1/accounts/{account_id}/portals/ |
Modify the name of a new pocket, its deposit strategy, its reinvestment strategy.
Customer systems:
Get the parameters that must be modified for an existing pocket.
Send to Jiko a pocket modification (patch) request, providing the pocket's name, deposit and reinvestment strategies.
Update the other customer's treasury, payment and accounting systems.
| Step | Purpose | Jiko API Endpoints |
|---|---|---|
| 1 | Get the list of all your pockets and retrieve the Id of the pocket to edit. | GET /api/v2/pockets/ |
| 2 | Edit a specific pocket. | PATCH /api/v2/pockets/{pocket_id}/ |
Provide your external bank with the routing number and the specific account number of the Jiko pocket to fund. Knowing that each Jiko pocket is assigned its own distinct account and routing numbers.
Customer systems:
Get from Jiko the id of the pocket to fund.
Get from Jiko the corresponding bank account number and routing number.
Initiate a funding transfer from an external bank account.
Monitor incoming funds in Jiko.
| Step | Purpose | Jiko API Endpoints |
|---|---|---|
| 1 | Get the list of all your pockets, and retrieve the id of the pocket to fund. | GET /api/v2/pockets/ |
| 2 | Get the account number/routing number for this pocket. By retrieving the portal configured for this pocket, passing the pocket's id as account_id parameter. A portal is the representation of a pocket from the perspective of the outside world, and includes the account number and routing number for a given pocket.Note: the current version assigns a single portal to each pocket. A future version may let you add portals, to use different account numbers (or Jiko network addresses) depending on your counterparty. | GET /api/v1/accounts/{account_id}/portals/ |
| 3 | Get the balance of the pocket, to monitor incoming funds. | GET /api/v2/pockets/{pocket_id}/ |
| 3b | Receive a webhook-based notification of incoming funds. | ToBeDetailed |
Deposit funds into a pocket, for that pocket to safeguard cash, earn a return, and be available to pay third-parties if and when needed.
Funds can be added to a pocket in the following ways:
| Funding type | Description | Payment Rails |
|---|---|---|
| Transfer from an external bank account | Transfer funds from one of your external bank accounts. Important: you must previously register this external bank account at Jiko. | ACH, Wire, Swift |
| Internal transfer between Jiko pockets | Transfer funds from another Jiko pocket of the same entity. See Fund Transfer between Your Pockets (Same-entity). | Jiko |
| Incoming payments from a third-party | Receive payments from third-parties via enabled payment rails. | ACH, Wire, Swift, JikoNet |
Retrieve the current value of a pocket, or of all pockets at the same time. For monitoring liquidity and automating treasury decision-making.
Customer systems:
Get from Jiko the list of pockets with their balance information.
Alternatively, get from Jiko the balance information for a specific pocket whose Jiko Id is known already by customer systems.
Update customer dashboards, workflows, or decision engines (example: enabling or blocking payment initiation based on balance).
Trigger additional actions, such as payment initiation, funding or sweeping, based on the received balance.
| Step | Purpose | Jiko API Endpoints |
|---|---|---|
| 1 | Get a list of bank transactions across all pockets. With the ability also to filter pockets, transaction types (ACH, Wire, On_Us, Fee), booking dates/times, amounts, and debit/credit direction. | GET /api/v2/transactions/ |
| 1b | Alternatively, get a list of bank transactions delivered in CSV format, instead of the json response format provided by the previous endpoint. | GET /api/v2/transactions.csv |
Query bank transactions for new activity, as well as retrieve a list of transactions occurring within a specified date/time range. Bank transactions include:
New fund deposits and withdrawals.
Incoming and outgoing third-party payments (when applicable).
Fees...
With information about the transaction type: ACH, Wire, and On Us ("On Us" transactions are same-entity transfers between Jiko pockets as well as JikoNet transfers to/from external counterparties).
Note: this real-time inquiry on bank transactions does not include the Jiko-initiated automated sweeps between the pocket's bank account and its linked brokerage account. Sweep transactions continuously reset the balance of the bank account to zero. Sweep transactions are available in the end-of-day Bank statement report: see Export Reporting.
Customer systems:
Identify the pocket(s) to query (store their Ids in the customer system or dynamically retrieve them from Jiko).
Send to Jiko a request for this range of pockets, dates/times, amounts, transaction types and retrieves the most up-to-date transaction activity
Feed the data into customer dashboards, monitoring tools, reconciliation engines, or alerting mechanisms.
| Step | Purpose | Jiko API Endpoints |
|---|---|---|
| 1 | Get a list of bank transactions across all pockets. With the ability also to filter pockets, transaction types (ACH, Wire, On_Us, Fee), booking dates/times, amounts, and debit/credit direction. | GET /api/v2/transactions/ |
| 1b | Alternatively, get a list of bank transactions delivered in CSV format, instead of the json response format provided by the previous endpoint. | GET /api/v2/transactions.csv |
<Section in progress>
| Funding type | Description | Payment Rails |
|---|---|---|
| Withdraw to a bank account | Transfer funds to one of your external bank accounts (which must be previously registered at Jiko). | Wire, Swift |