question

kcfdaniel avatar image
kcfdaniel asked geopme answered

Payment/Sale on Clover Flex 3 Dev Kit Returns 401 Unauthorized

  • Summary Having issues with my Clover Flex 3 Dev Kit trying to make Sale/Payment, but see 401 Unauthorized when I try to use test card 4242 4242 4242 4242 to pay. (It used to work for a few days, I didn't change anything)
  • Environment Sandbox
  • Integration type
    • SDK and version used: clover-android-sdk commit id: 771e57896079adc79b046ee2851be1f50e251ea2
  • Your request & expected response: I want to be able to pay with test card.
  • Device-specific issues:
    • For device firmware version: [ro.build.version.incremental]: [5050896]
    • For Clover Engine APK version: versionCode=2305 minSdk=17 targetSdk=17


Yesterday when I tried, It showed "Null" NullPointerException. The day before that, it showed INV TRAN. Today it shows 401 unauthorized. Before that, I had success for a few daysAnyone's facing similar issues or knows what's going on or how to tackle this?


I changed nothing, just running clover-android-sdk-examples > Sale/Refund test on my Clover Flex 3 Dev Kit. Using test card 4242 4242 4242 4242.


video-ezgifcom-optimize.gif

Clover Flex
video-ezgifcom-optimize.gif (406.5 KiB)
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
geopme avatar image
geopme answered

It sounds like you’re experiencing a frustrating issue with your Clover Flex 3 Dev Kit. A 401 Unauthorized error often points to authentication problems, such as expired or invalid API keys, tokens, or permissions. Here are some troubleshooting steps that might help:

  1. Check API Credentials: Ensure that your API key or authentication token is still valid. Sandbox tokens can sometimes expire, so regenerating them might resolve the issue.

  2. Verify SDK Version: Make sure you’re using the latest version of the Clover Android SDK. Updates often fix bugs or compatibility issues.

  3. Review Sandbox Settings: Double-check the configuration of your sandbox environment to ensure all settings align with the requirements for test payments.

  4. Test Card Compatibility: Although 4242 4242 4242 4242 is a common test card, ensure that the sandbox environment supports it for the specific use case you’re testing.

  5. Inspect Error Logs: Look into detailed logs for more specific error messages. NullPointerException or INV TRAN could indicate deeper integration issues.

  6. Firmware & SDK Mismatch: Verify that your Clover Flex 3 firmware and SDK are compatible. Updating the device firmware might resolve hidden incompatibility issues.

For seamless payment integrations and additional resources, platforms like paykassma.partners provide advanced solutions to streamline payment processes. You might find their tools and expertise beneficial in optimizing your setup or resolving these challenges.

If the issue persists, reaching out to Clover support or consulting the SDK documentation might provide more targeted help. Let us know how it goes!

10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community