Compatibility Matrix & Changelog
This page names the SDK artifact each guide applies to, the dependency versions it was validated against, and what has changed. If your project uses a different artifact, review this page before copying behaviour from the integration guides.
Compatibility matrix
The values below describe the current Android Payments SDK artifact (payments_sdk_v20220912).
| Item | Value |
|---|---|
| AppInChina Android Payments SDK artifact | payments_sdk_v20220912 (internal build acp-v20220222-prod-production) |
FastJSON 1.x (com.alibaba:fastjson) | Pin 1.2.83. The SDK uses only stable core FastJSON 1.x APIs (no autotype), so it is compatible with any 1.2.x; 1.2.83 is chosen as the most-hardened 1.x release. Do not use old versions such as 1.1.70.android. |
Alipay SDK (com.alipay.sdk:alipaysdk-android) | 15.8.33 |
WeChat SDK (com.tencent.mm.opensdk:wechat-sdk-android-with-mta) | 6.8.0 |
| Minimum / target Android API | minSdkVersion 14 / targetSdkVersion 30 (from the SDK manifest) |
| Known device/OS exclusions or caveats | None published. All FastJSON 1.x is end-of-life; older 1.x builds carry known CVEs. A FastJSON2 + Xiaomi/HyperOS report is under internal review and is not a published SDK limitation — see FastJSON dependency issues. |
FastJSON 1.x (com.alibaba:fastjson) and FastJSON2 (com.alibaba.fastjson2:fastjson2) are different dependency families. This SDK uses FastJSON 1.x. See Prerequisites §3.2.
Behaviour confirmed for this artifact
These points are specific to payments_sdk_v20220912 and should be re-validated if the artifact changes:
startPayment()does not report a final result. It creates the order (POST /order.json) and launches the wallet; it does not deliver a paid/failed/cancelled result to the host app. Grant access only after backend verification — see Server Verification and Entitlements.- Alipay opens the supplied
nextActivityunconditionally after the wallet returns; the launch is not a payment confirmation. See Android §7.6. - WeChat returns to
WXPayEntryActivity, notnextActivity, and requires a successfulinitPayTools()before the first payment. See Android §7.7. queryHistoryOrder(...)callsGET /history.json. See the API Reference.- Error
99999is a generic client-side exception path, not a specific payment decline. See Troubleshooting.
Changelog
| Date | Change | Action required |
|---|---|---|
| 2026-08-04 | FastJSON version confirmed: the SDK uses only stable core 1.x APIs (no autotype) → compatible with any 1.2.x; pin 1.2.83. Android minSdk 14 / targetSdk 30. | Pin 1.2.83; remove any old FastJSON 1.x (e.g. 1.1.70.android) from the release graph. |
| 2026-08-04 | Documented artifact-specific behaviour: authoritative payment-completion rule; Alipay nextActivity vs WeChat WXPayEntryActivity return routes; initPayTools() WeChat prerequisite; 99999 as a generic client-side exception. | Re-test post-payment handling against your backend; do not treat wallet return/callback as success. |
| 2026-08-04 | FastJSON guidance corrected: the dependency is required by the AppInChina SDK (legacy FastJSON 1.x), pinned, and distinct from FastJSON2. | Pin the FastJSON 1.x version; keep any FastJSON2 explicit and tested. |
| 2026-08-03 | /history.json method corrected to GET across the API reference, history guide, and examples. | Update any client code that used POST /history.json. |
When a new SDK artifact is released, Engineering revalidates the Quick Start, payment-lifecycle diagrams, dependency block, endpoint examples, and troubleshooting/error mapping before the docs mark that version as current.