Go-Live Checklist
Use this checklist before enabling Network Identity & Risk Signals in production. Share it with your integration team.
Credentials & setup
- API key received from tyntec and stored securely (not hardcoded in client-side code)
- Base URL confirmed: https://api.tyntec.com/network-signal/v1
- apiKey header included in all requests
Coverage
- Coverage confirmed for your target geographies with your tyntec account manager
- Handling for 404 NOT_FOUND implemented — treated as inconclusive, not as pass or fail
- Fallback path to standard OTP or password in place for unsupported numbers/operators
SIM Swap integration
- POST /sim-swap/check called before every OTP dispatch
- maxAge value chosen and documented for each use case (default 240, max 2400 minutes)
- swapped=true results in OTP being blocked — step-up or rejection applied
- POST /sim-swap/retrieve-date integrated where timestamp is needed for audit or risk scoring
Call Forwarding integration
- POST /call-forwarding/unconditional/check called before every voice OTP dispatch
- active=true results in OTP being blocked — step-up or rejection applied
- Distinction between unconditional forwarding (block) and other forwarding types understood
Call Forwarding integration
- POST /call-forwarding/unconditional/check called before every voice OTP dispatch
- active=true results in OTP being blocked — step-up or rejection applied
- Distinction between unconditional forwarding (block) and other forwarding types understood
Device Swap integration
- POST /device-swap/check integrated at login and/or pre-transaction
- swapped=true used as compound signal alongside SIM Swap for enhanced fraud scoring
- maxAge value set appropriately for your risk threshold
Error handling
- 400 errors: request validation in place — phone numbers always sent in international format
- 401 / 403 errors: API key rotation procedure documented
- All error codes and their meanings reviewed by the integration team
Testing
- End-to-end test: SIM Swap check returns swapped=true — OTP correctly blocked
- End-to-end test: Call Forward check returns active=true — OTP correctly blocked
- End-to-end test: all signals negative — flow proceeds normally
- Combination test: SIM Swap + Device Swap both positive — high-risk action correctly blocked
Go-live
- tyntec account manager notified of go-live date
- Monitoring and alerting configured for API error rates
- Runbook in place for common failure scenarios (quota exceeded, operator unavailable)
- Support team briefed on Network Identity & Risk Signals behaviour and what users may experience
Need help? For technical support or integration questions, contact your tyntec account representative or email support@tyntec.com. Full API documentation: https://api.tyntec.com/reference/network-signals/current.html#network-signal-api