TROUBLESHOOTING · DEVELOPER RESOURCES
Help with Testing with fictional data
This page focuses on the guide you were reading. Work through the relevant checks below, then send us a question if the issue is still unresolved.
01
Start with your testing with fictional data setup
These are checks drawn from this feature's own instructions.
- Never use real PHI in RL Health tests.
- Do not confuse payment test-mode confirmation with production settlement.
02
Common problems in Developer resources
Choose the problem closest to what you are seeing. Each one includes practical checks and a safe next step.
An expected endpoint or webhook is not available
- Check whether the document describes a conceptual API rather than a published contract.
- Verify the exact supported integration and test environment.
- Do not use internal or undocumented endpoints in a production dependency.
Public API contracts will be documented only after they are supported.
An integration behaves differently on retry
- Check request authentication and signature verification.
- Handle repeated and out-of-order events idempotently.
- Compare a sandbox event with the processor's authoritative state.
Avoid logging tokens, secrets, or client-sensitive payloads in support requests.
03
Still not resolved?
When you contact support, tell us what you expected, what happened instead, the non-sensitive error text (if any), and roughly when it occurred. The form will automatically include Testing with fictional data as the topic.
Please do not include passwords, security codes, payment card details, client health records, or any other sensitive information.