Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Report NFC Wallet SDK issues

General notes

To troubleshoot efficiently, Thales support needs the key details up front.

Missing context usually means more back-and-forth and a slower resolution.

Include the following in every issue report:

  1. NFC Wallet SDK version and build type

    • Specify the SDK version.

    • Specify whether you use the dev or release build.

  2. Issue type

    • Crash (include a crash log).

    • SDK error (include the error details).

    • User experience issue

    • Other (describe clearly).

  3. Use case

    • Initialization or wallet secure enrollment (WSE).

    • Tokenization (create and provision a digital card).

    • LCM (suspend, resume, delete).

    • Other (describe).

  4. Issue summary

    • Describe what happened and when it started.

    • For crashes, attach the stack trace. Make sure that the stack trace is already decoded by the application mapping files (generated at application build time).

    • For SDK errors, include:

      • The last NFC Wallet SDK API method called.

      • The error code and message.

      • Any additional fields from the error object.

    • For user experience issues, attach a screenshot or screen recording.

  5. Steps to reproduce

    • Provide an exact, numbered sequence.

    • Call out prerequisites (configuration, test account state, network, etc.).

    • Clarify whether it is systematic (100% reproducible) or intermittent.

  6. Expected behavior

    • Describe what you expected versus what you observed.

    • Note: Sometimes a misinterpretation of the SDK feature functionality is reported as an issue.

  7. Environment

    • Specify Pre-Production or Production.

    • Specify distribution (internal testing, beta, or public end users).

  8. Affected devices and Android versions

    • List device models and Android versions where the issue reproduces.

    • List devices where the issue does not reproduce (if known).

  9. Occurrence rate

    • Provide counts and a time window (for example, “2 out of 10 attempts” or “10 times in 24 hours”).

    • Estimate the percentage of end users affected.

  10. Affected wallet instance and digital card

  11. NFC Wallet SDK logs

    • If you can reproduce in a controlled environment, reproduce using a build of your digital wallet application that integrates the NFC Wallet SDK dev build.

    • Follow Retrieve logs from an Android device.

Do not share PAN, CSC/CVV2, OTP, or other end-user sensitive data in tickets. Use identifiers such as digitalCardID instead.

Provide use case-specific details

Some use cases need extra context. Add the details below, in addition to the standard template.

Avoid generic statements like “Tokenization fails” or “payment doesn’t work”. They block triage and slow down resolution.

  1. Confirm the expected flow.

    • Is this the green flow or yellow flow?

    • Did wallet secure enrollment complete successfully?

  2. Pinpoint where the flow stops.

    • What is the last NFC Wallet SDK API method called?

    • What is the last NFC Wallet SDK API method that completes successfully?

  3. Share the exact error (if any).

    • What are the error code and message?

    • What additional fields are returned in the error object (if present)?

Issue report template

Use this template when reporting an issue to Thales support.

Replace <PLEASE FILL HERE> with your values. Use N/A when not applicable.

PreviousCompute the application binding keyNextRetrieve logs from an Android device

Last updated

Was this helpful?