Skip to main content
PIK maintains a full transaction ledger for every account. You can retrieve history via the API at any time, filter by date range or type, and export for reconciliation with your accounting system.

Transaction Types

TypeDescription
payment_inInbound payment received and settled to the wallet
payment_outOutbound payout sent from the wallet
fx_conversionCurrency conversion between wallet balances
transfer_inFunds moved into this wallet from another PIK wallet
transfer_outFunds moved from this wallet to another PIK wallet
feePlatform fee or PIK fee deducted
reversalReturned payout credited back to wallet

Retrieve Transaction History via API

http
GET /api/v1/accounts/{account-id}/transactions
Authorization: Bearer YOUR_PLATFORM_API_KEY
x-on-behalf-of: {connected-account-id}
Query parameters:
ParameterTypeDescription
currencystringFilter by currency: AUD, USDT, USDC, USD, HKD, SGD
typestringFilter by type: payment_in, payment_out, fx_conversion, etc.
from_dateISO 8601 dateReturn transactions on or after this date
to_dateISO 8601 dateReturn transactions on or before this date
limitintegerResults per page. Max 100, default 20
cursorstringPagination cursor from previous response
Example — retrieve all settled USDT payments in April 2025: http
GET /api/v1/accounts/{account-id}/transactions
  ?currency=USDT
  &type=payment_in
  &from_date=2025-04-01
  &to_date=2025-04-30
  &limit=100

Transaction Response Fields

Each transaction in the response includes:
FieldDescription
transaction_idUnique transaction identifier
typeTransaction type (see table above)
currencyCurrency code
amountTransaction amount as decimal string
feeFee deducted (if applicable)
net_amountAmount after fee
referenceReference string set at time of transaction
statussettled, pending, failed
created_atISO 8601 timestamp
counterpartyCounterparty details where applicable

Matching Payments to Internal Records

The reference field is the primary reconciliation key. When creating a payment request or payout, always set your internal order ID or invoice number as the reference. PIK records this on the transaction and returns it in every API response and webhook payload. Reconciliation workflow:
  1. Pull transactions for the period using GET /api/v1/accounts//transactions
  2. For each transaction, match the reference field to your internal records
  3. Mark matched records as reconciled
  4. Flag unmatched transactions for manual review

Exporting Data

To export a full transaction history, paginate through the transactions endpoint using the cursor field until all pages are retrieved, then combine into a single dataset. PIK does not currently offer a one-click CSV export via the API. Transform the JSON response into CSV using your preferred tooling. Dashboard export: Transaction history can be exported as CSV from the PIK Dashboard under Transactions > Export.

Accounting Integrations

PIK does not currently offer native integrations with Xero, QuickBooks, or MYOB. Use the API to pull transaction data and import into your accounting system using the CSV export or a custom integration. For enterprise integration support, contact hi@pik.global.