Simulate inbound payment status request
API reference
Simulate receiving an inquiry about the status of a payment transaction
This API can only be run in the Cross River Sandbox
Endpoint: /rtp/payments/{id}/simulated-inbound-payment-status-request
POST
https://sandbox.crbcos.com/rtp/v1/payments/{id}/simulated-inbound-payment-status-request
curl -X POST https://sandbox.crbcos.com/rtp/v1/payments/{id}/simulated-inbound-payment-status-request \\
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \\
-H "Content-Type: application/json"Use cases
- Test payment flows in sandbox environment without real network transmission
- Validate integration with Cross River APIs before production
- Develop and debug payment handling workflows
- Train staff on payment processing scenarios
Error codes
Code | Scenario | Resolution |
|---|---|---|
2018 | Invalid Debtor | Verify request parameters and retry |
2017 | Payments of $3,000 or more require a complete debtor address | Verify request parameters and retry |
2007 | Direction not inbound | Verify request parameters and retry |
3001 | Unauthorized | Verify Bearer token is valid and not expired |
3002 | Insufficient permissions | Verify user has required permission for this operation |
Business rules
- Requires valid Bearer token with permissions: Permissions.Payments.Simulate
- Request validation performed before processing
- Errors return 400 Bad Request with detailed error information
- Rate limiting may apply to prevent abuse