Simulate inbound payment ack
API reference
Simulate receiving acknowledgment from the receiving bank that your outbound payment was accepted
This API can only be run in the Cross River Sandbox
Endpoint: /rtp/payments/{id}/simulated-inbound-payment-ack
POST
https://sandbox.crbcos.com/rtp/v1/payments/{id}/simulated-inbound-payment-ack
curl -X POST https://sandbox.crbcos.com/rtp/v1/payments/{id}/simulated-inbound-payment-ack \\
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \\
-H "Content-Type: application/json" \\
-d '{
"paymentAckType": "sample_value",
"additionalInfo": "sample_value"
}'Use cases
- Test payment acknowledgment workflows in sandbox
- Validate successful payment completion handling
- Simulate network confirmation for integration testing
- Verify payment status transitions after acknowledgment
Error codes
Code | Scenario | Resolution |
|---|---|---|
2041 | Payment must be a credit transfer | Verify request parameters and retry |
2010 | Payment must be outbound | Verify request parameters and retry |
2030 | Credit Transfer status must be Completed | Verify request parameters and retry |
2031 | Payment already has an existing Payment Ack in process | 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