Managing Transactions

To monitor and manage transactions efficiently, you can retrieve transaction data, add memos, and attach receipts using the available API endpoints.

​

Retrieving transactions

Retrieve transactions from the GET /issuing/transactions endpoint. For a dashboard-like view, you can fetch transactions by company, user, or card ID. The response includes:

• Cursor-based pagination for handling large datasets. The response is a plain array; to fetch the next page, pass the last item’s id as the cursor query parameter.
• Transaction types categorized by a type field.
• Structured schemas for different transaction types.

This allows for efficient querying and filtering of transaction records.

​

Transaction Types

You can fetch transactions by type as well. Use the type param, which is an array parameter that accepts one or more of the values below:

Type	Description
spend	Regular spend transactions of the cardholder.
collateral	Transactions related to the user’s or company’s collateral contract.
payment	Payments made (usually via a liquidation event) against the posted balance of the user or company.
fee	Fees charged through the Rain Charge User API or Charge Company API.
transfer	Virtual-account money movement, including onramps and offramps.
verification	Verification-related transactions.

​

Filtering by status

Use the status param to return only transactions in a given state, such as the pending authorizations still waiting to settle. It accepts one value:

Status	Description
pending	The transaction has not settled and was not declined or reversed.
reversed	The authorization was reversed before it settled.
declined	The authorization was declined.
completed	The transaction has settled.

The status filter applies to spend and payment transactions only. When you set status without type, the response excludes all other transaction types. Payment transactions report only pending and completed, so filtering by reversed or declined returns spend transactions alone.

If you combine status with a type value other than spend or payment, such as type=fee, the request returns 400 Bad Request.

For example, to list only declined transactions for a user:

curl -X GET "https://api.rain.xyz/v1/issuing/transactions?userId=11111111-1111-1111-1111-111111111111&status=declined" \
  -H "Api-Key: YOUR_API_KEY"

​

Adding a memo to a transaction

To store additional context about a transaction, update it by passing a value to the memo field.

​

Example: Updating a transaction with a memo

Use the update transaction endpoint to attach a memo. The memo will be stored and returned with the transaction details.

​

Managing transaction receipts

For spend transactions, you can attach and retrieve receipts to enhance record-keeping.

​

Attaching a receipt

• Use the upload receipt endpoint.
• Send the receipt file as a multipart/form-data payload under the receipt key.

​

Fetching a receipt

• Call the get transaction receipt endpoint.
• The receipt will be returned as an application/octet-stream.