X-Telcom / Integration acceptance
Validate every response between your backend and the palm vein SDK.
The algorithm request succeeded. Did the terminal finish its workflow?
Use this practical acceptance worksheet to check registration, query and deletion responses before handing over your integration.
01 / FOLLOW THE RESULT BACK
Check completion at three levels.
Transport
Did the request and response reach their destinations? Record the observed transport status without treating it as proof of biometric success.
Algorithm operation
What does the documented service response say? Compare the actual content with the specification for the corresponding operation.
SDK workflow
Did the backend return the expected response format, and did the terminal complete its registration, identification or deletion flow?
02 / OPERATION-BY-OPERATION REVIEW
One checklist for each return path.
Select the operation you are validating. Mark only the checks your team has confirmed with evidence.
Your selections stay in this browser session only. Nothing is submitted. This is a planning worksheet, not an automated API test or certification.
0 of 15 checks confirmed
Registration acceptance
Query acceptance
Deletion acceptance
03 / LOCATE THE BREAK
Start with the symptom you observed.
04 / MAKE SUPPORT ACTIONABLE
Send a reproducible problem, with the right context.
Generate a short technical brief for your team or support contact. Include sanitised observations and the expected behaviour.
The generator runs locally in your browser. It does not send or retain your input. The download buttons create plain-text files.
RESPONSE VALIDATION QUESTIONS
Clarify what a successful test proves.
Does an HTTP success status prove the SDK flow is complete?
No. Check the documented response content and confirm that the terminal completes the expected operation. Transport success alone is not an application acceptance result.
Can our backend return a custom success response?
Internal response structures can be managed within your backend, but the response returned to the SDK must match its expected format.
Where do we get exact fields and error codes?
Use the API documentation supplied for your SDK and Algorithm Server version. This page is an acceptance worksheet, not a replacement endpoint specification.
What if the SDK works directly but fails through our backend?
Compare the forwarded operation and returned response with the working direct test. Check field handling, payload representation and the return path before changing algorithm settings.
Does a successful identification approve payment?
No. Your business platform handles account checks, payment authorisation and the final transaction result.
Can we test Small and Large Model SDKs in one build?
No. These are separate, decoupled systems. Their SDKs should not be used together in the same app build. This worksheet concerns the Large Scale integration.
X-Telcom technical support
Review your integration evidence.
Share the operation, relevant version references and sanitised reproduction details so we can assess the next step.