Softpay integration issues can arise due to app settings or incorrect API configurations. This article provides solutions to common problems encountered when using Softpay with AppSwitch on Android or Cloud API.
Common Issues with Softpay Integration
1. Softpay Does Not Open Automatically (AppSwitch or Cloud API)
Softpay may intermittently fail to open or come to the foreground on its own. This affects both integration methods:
AppSwitch on Android: switching to the Softpay app fails or the app is not discoverable.
Cloud API: a cloud-initiated transaction does not start automatically, and the payment only begins after the user manually opens the app or taps the notification on the device.
The most common cause for both is Android placing the Softpay app into a hibernated or paused state. This is particularly common on devices running Android 13 or later. When the app is hibernated or paused, it cannot be switched to (AppSwitch) or brought to the foreground automatically (Cloud API), so transactions wait for the app to be opened manually.
Steps to Fix:
Open the Android Settings on your device.
Navigate to the Softpay app settings.
Go to Permissions or App Info → App Battery/Permissions Settings.
Disable the setting that hibernates or pauses unused apps. This setting may be labeled as:
"Pause app activity if unused"
"Manage app if unused"
"Remove permissions and free up space"
Similar wording depending on your Android version.
After disabling this setting, Softpay should remain active in the background. AppSwitch will open the app reliably, and Cloud API initiated transactions will start automatically without needing to open the app or tap the notification manually.
2. App Does Not Resume After a Softpay Transaction (Switch-Back) Using Cloud API
When using the Cloud API, issues with app resumption after a Softpay transaction can occur if the activityToResume parameter is defined in multiple places. Softpay uses this parameter to fire the resume intent upon transaction completion, and defining it twice can cause conflicts.
Steps to Fix:
Set the
activityToResumeparameter in only one place:Either in the REST request.
Or in the intent call.
Ensure your request payload uses the correct, case-sensitive field names. For example:
Use
optionsinstead ofOptions.
By following these steps, you can prevent conflicts and ensure seamless app resumption.
Additional Tips for Ensuring Seamless Functionality
Regularly check your app settings to ensure compatibility with the latest Android updates.
Review API documentation to confirm correct parameter usage and field naming conventions.
Related Topics
Setting up Softpay in Sandbox Environment
Best Practices for AppSwitch Integration
Troubleshooting API Errors in Softpay
By following these troubleshooting steps and best practices, you can resolve common issues and ensure a smooth experience with Softpay integration.