Account & Reports

Know when a collateral contract is deployed on-chain and when daily BIN report files are ready to fetch.

These webhooks cover account-level events: collateral contract creation for Rain-managed programs, and BIN report file delivery for BIN-Sponsorship programs.

The following events are available:

Event	Description
contract.created	A collateral contract is created for an approved user.
report.created	BIN report files have arrived for a BIN-Sponsorship program.

contract.created

Blockchain tenants only:

On blockchain tenants where each user posts their own collateral, Rain creates a collateral contract for each approved user. Pooled-collateral programs deploy a single contract at setup, so they do not receive a contract.created event per cardholder.

This webhook is triggered whenever a new collateral contract is created within the system.

Payload

{
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "resource": "contract",
    "action": "created",
    "version": "1.0.1",
    "body": {
        "id": "cc_abc123",
        "userAddress": "0x1234567890abcdef1234567890abcdef12345678",
        "chainId": "1",
        "proxyAddress": "0xabcdef1234567890abcdef1234567890abcdef12",
        "depositAddress": "0xfedcba0987654321fedcba0987654321fedcba09",
        "controllerAddress": "0x9876543210fedcba9876543210fedcba98765432",
        "contractVersion": 1,
        "userId": "usr_def456"
    }
}

Field	Type	Description
id	string	The collateral contract ID
userAddress	string	The user’s wallet address associated with the contract
chainId	string	The blockchain chain ID (for example, "1" for Ethereum mainnet)
proxyAddress	string (optional)	The proxy contract address
depositAddress	string (optional)	The address where collateral should be deposited
controllerAddress	string	The coordinator or controller contract address. Optional in version 1.0.0; always present from 1.0.1.
contractVersion	number	The version of the smart contract
userId	string (optional)	The Rain user ID associated with the userAddress. Rain omits this field when it finds no matching user.

report.created

BIN-Sponsorship program only:

This section applies to BIN-Sponsorship Programs. Take note of this information if you are using a BIN-Sponsorship Program.

The report.created webhook is triggered when the processor’s BIN report files have arrived in our storage servers. Reports for the previous day are available at 3pm ET.

The webhook provides:

• The year, month, and day of the files that have arrived.
• The format of the BIN reports that have arrived from the processor

Payload

{
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "resource": "report",
    "action": "created",
    "version": "1.0.0",
    "body": {
        "id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
        "year": "2026",
        "month": "01",
        "day": "27",
        "format": "json"
    }
}

Field	Type	Description
id	string	Deterministic report ID (based on tenant, date, and format)
year	string	The year of the BIN report files that arrived (for example, "2026")
month	string	The month of the BIN report files, zero-padded (for example, "01")
day	string	The day of the BIN report files, zero-padded (for example, "27")
format	string	The format of the BIN report: csv or json

Use the report date fields (year, month, day) and the format to fetch the report with the Get a tenant’s report endpoint.

What’s next

Payment routes

Track when a payment route becomes active and ready to receive deposits.

Raindrops

Track Raindrops balance requests and the travel redemption lifecycle.