Sandbox simulations: funding address and collection status

You can now move a pending funding address to active or rejected, and move a collection from under_review to awaiting_funds, on demand in sandbox. This lets you test the full funding and collection flow directly.

Impact

• Breaking change: No. These are two new sandbox-only endpoints. Existing integrations keep working.
• Who is affected: Clients testing fiat funding addresses and collections in sandbox.
• Environments: Sandbox only (https://sandbox.payments.reap.global). Not available in production.

Endpoints

1. Simulate funding address status - POST /api/simulate/funding-addresses/{addressId}/status
2. Simulate collectio status - POST /api/simulate/collections/{collectionId}/status

How simulating a funding address works

1. Create a funding address. It starts as pending.
2. Call Simulate funding address status with status set to active or rejected. For rejected, you can also pass an optional failureReason, which is returned in the webhook.
3. The call returns right away. The funding address updates a few seconds later. Calling again once the address is no longer pending returns 409.
4. You will receive a funding_address_status_update webhook when the address changes.

How simulating a collection works

1. Create a collection and upload its documents. The collection moves to under_review. In sandbox, screening does not complete on its own for sandbox businesses, so it waits for you.
2. Call Simulate collection status with status set to awaiting_funds. This passes screening for you.
3. The collection moves to awaiting_funds, with its paymentLink and transferReference. Calling again returns 409, because the collection is no longer under_review.
4. You will receive a collection_status_update webhook with the new status.