Fix V3 payment field serialization mismatch with WeChat-expected JSON keys (`package`, `partnerid`, `prepayid`) by Copilot · Pull Request #3954 · binarywang/WxJava

Copilot · 2026-04-07T09:12:13Z

V3 payment result objects used Java field names that, when serialized by Gson, produced JSON keys incompatible with WeChat's payment APIs. Specifically:

packageValue was serialized as packageValue instead of the required package
partnerId / prepayId in WxPayUnifiedOrderV3Result.AppResult were serialized as camelCase instead of the required all-lowercase partnerid / prepayid

Changes

WxPayUnifiedOrderV3Result (JsapiResult) — add @SerializedName("package") to packageValue
WxPayUnifiedOrderV3Result (AppResult) — add @SerializedName("package") to packageValue; add @SerializedName("partnerid") to partnerId; add @SerializedName("prepayid") to prepayId
CombineTransactionsResult (JsapiResult, AppResult) — add @SerializedName("package") to packageValue
TransactionsResult (JsapiResult, AppResult) — add @SerializedName("package") to packageValue

Result

// Before (WxPayUnifiedOrderV3Result.AppResult)
{ "packageValue": "Sign=WXPay", "partnerId": "1900000109", "prepayId": "wx..." }

// After
{ "package": "Sign=WXPay", "partnerid": "1900000109", "prepayid": "wx..." }

Java getter/setter names (getPackageValue(), getPartnerId(), getPrepayId(), etc.) are unchanged — only the serialized JSON keys are affected.

New tests in WxPayUnifiedOrderV3ResultTest verify that Gson output for both JsapiResult and AppResult uses the correct WeChat-expected field names (package, partnerid, prepayid) and does not contain the old camelCase keys.

Agent-Logs-Url: https://github.com/binarywang/WxJava/sessions/4f76043e-c058-4838-8d60-a43a1c878544 Co-authored-by: binarywang <1343140+binarywang@users.noreply.github.com>

augmentcode · 2026-04-07T13:22:21Z

🤖 Augment PR Summary

Summary: Fixes WeChat Pay V3 payment parameter JSON output so the key is package (as required by WeChat) rather than the Java field name packageValue.

Changes:

Adds @SerializedName("package") to packageValue in multiple V3 payment result DTOs (JSAPI/App variants).
Updates unified-order V3 result bean to ensure Gson serialization matches WeChat client API expectations.
Adds unit tests to verify Gson output contains package and not packageValue for both JSAPI and App results.

Technical Notes: This change is Gson-specific (via com.google.gson.annotations.SerializedName) and keeps Java getters/setters unchanged.

_{🤖 Was this summary useful? React with 👍 or 👎}

augmentcode

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-04-07T13:22:22Z

...ava-pay/src/main/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3Result.java

    private String timeStamp;
    private String nonceStr;
+    /**
+     * 由于package为java保留关键字，因此改为packageValue，序列化时会自动转换为package字段名


packageValue 这里的注释写“序列化时会自动转换为package字段名”，但实际是依赖 Gson 的 @SerializedName("package") 才会生效；如果调用方用其他 JSON 库（如 Jackson）仍可能输出 packageValue。考虑在注释里明确这是 Gson 序列化行为以避免误导。

Severity: low

Other Locations

weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3Result.java:116

weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/result/CombineTransactionsResult.java:77

weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/result/CombineTransactionsResult.java:97

weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/ecommerce/TransactionsResult.java:69

weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/ecommerce/TransactionsResult.java:88

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-04-07T13:22:22Z

...pay/src/test/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3ResultTest.java

+    Assert.assertEquals(jsapiResult.getPackageValue(), "prepay_id=" + testPrepayId);
+
+    // 验证JSON序列化后字段名为package（微信官方要求）
+    Gson gson = new Gson();


这里用 new Gson() 来验证序列化字段名，可能与项目内实际使用的 Gson 配置（例如 WxGsonBuilder.create() 或统一的 GsonBuilder 实例）不一致。为避免后续 Gson 配置调整导致测试与真实序列化行为偏离，考虑复用项目里支付模块的 Gson 创建方式。

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

Copilot

Pull request overview

该 PR 修复微信支付 V3 拉起支付参数对象在使用 Gson 序列化时，packageValue 被错误序列化为 packageValue（而非微信端要求的 package）的问题，从而提升与微信 wx.requestPayment / APP 支付拉起参数的兼容性。

Changes:

为多个 V3 支付结果对象中的 packageValue 增加 @SerializedName("package")，确保 JSON key 为 package
新增单元测试，验证 WxPayUnifiedOrderV3Result 的 JsapiResult / AppResult 序列化后包含 package 字段且不包含 packageValue

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3Result.java	为 `JsapiResult` / `AppResult` 的 `packageValue` 增加 `@SerializedName("package")`
weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/result/CombineTransactionsResult.java	为 `JsapiResult` / `AppResult` 的 `packageValue` 增加 `@SerializedName("package")`
weixin-java-pay/src/main/java/com/github/binarywang/wxpay/bean/ecommerce/TransactionsResult.java	为 `JsapiResult` / `AppResult` 的 `packageValue` 增加 `@SerializedName("package")`
weixin-java-pay/src/test/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3ResultTest.java	新增序列化测试用例，校验 `package` 字段名输出

Copilot · 2026-04-07T13:23:40Z

...ava-pay/src/main/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3Result.java

    private String appid;
    private String partnerId;
    private String prepayId;
+    /**
+     * 由于package为java保留关键字，因此改为packageValue，序列化时会自动转换为package字段名
+     */
+    @SerializedName("package")
    private String packageValue;
    private String noncestr;


WxPayUnifiedOrderV3Result.AppResult 目前只有 packageValue 增加了 @SerializedName("package")；但同一个对象里 partnerId / prepayId 字段如果用 Gson 序列化，JSON key 会变成 partnerId / prepayId，而微信 APP 支付参数要求的是 partnerid / prepayid（同模块里 CombineTransactionsResult/TransactionsResult 的 AppResult 也使用了全小写字段名）。建议为 partnerId、prepayId 同样补充 @SerializedName("partnerid") / @SerializedName("prepayid")（或统一字段命名策略），避免调用方直接序列化该对象时仍不兼容微信端。

Copilot · 2026-04-07T13:23:41Z

...pay/src/test/java/com/github/binarywang/wxpay/bean/result/WxPayUnifiedOrderV3ResultTest.java

+    WxPayUnifiedOrderV3Result.AppResult appResult =
+      WxPayUnifiedOrderV3Result.getAppPayInfo(testPrepayId, testAppId, testMchId, privateKey);
+
+    // 验证Java字段名仍为packageValue
+    Assert.assertEquals(appResult.getPackageValue(), "Sign=WXPay");
+
+    // 验证JSON序列化后字段名为package（微信官方要求）
+    Gson gson = new Gson();
+    JsonObject jsonObject = gson.toJsonTree(appResult).getAsJsonObject();
+    Assert.assertTrue(jsonObject.has("package"), "JSON中应该包含package字段");
+    Assert.assertFalse(jsonObject.has("packageValue"), "JSON中不应该包含packageValue字段");
+    Assert.assertEquals(jsonObject.get("package").getAsString(), "Sign=WXPay");


新增的 JSON 序列化测试目前只校验了 package/packageValue；但如果调用方直接用 Gson 序列化 AppResult，partnerId/prepayId 仍会输出为驼峰 key（partnerId/prepayId），与微信 APP 支付期望的 partnerid/prepayid 不一致。建议在同一组测试里也断言 partnerid/prepayid 的字段名与值（并在代码侧配合补齐 @SerializedName）。

binarywang · 2026-04-07T13:31:09Z

@copilot apply changes based on the comments in this thread

…ame注解，修复与微信官方API字段名不一致问题 Agent-Logs-Url: https://github.com/binarywang/WxJava/sessions/099513d0-4cde-45a3-850c-1afec934741c Co-authored-by: binarywang <1343140+binarywang@users.noreply.github.com>

Copilot · 2026-04-07T13:36:07Z

@copilot apply changes based on the comments in this thread

已在 49c1559 中处理：

为 WxPayUnifiedOrderV3Result.AppResult 的 partnerId 添加 @SerializedName("partnerid")
为 WxPayUnifiedOrderV3Result.AppResult 的 prepayId 添加 @SerializedName("prepayid")
在测试中增加对 partnerid/prepayid JSON 字段名的断言

现在序列化后与 CombineTransactionsResult/TransactionsResult 保持一致，符合微信官方 APP 支付参数要求。

Initial plan

bec6109

Copilot AI assigned Copilot and binarywang Apr 7, 2026

Copilot started work on behalf of binarywang April 7, 2026 09:12 View session

Copilot AI linked an issue Apr 7, 2026 that may be closed by this pull request

V3支付，组装预支付参数和官网字段不一致（packageValue 和 package字段） #3953

Open

Copilot AI and others added 2 commits April 7, 2026 09:18

修复测试文件中多余的空行

dd6d48e

Agent-Logs-Url: https://github.com/binarywang/WxJava/sessions/4f76043e-c058-4838-8d60-a43a1c878544 Co-authored-by: binarywang <1343140+binarywang@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix package value mismatch in V3 payment parameters~~ Fix V3 payment package field serialized as packageValue instead of WeChat-expected package Apr 7, 2026

Copilot AI requested a review from binarywang April 7, 2026 09:21

Copilot finished work on behalf of binarywang April 7, 2026 09:22

binarywang marked this pull request as ready for review April 7, 2026 13:20

Copilot AI review requested due to automatic review settings April 7, 2026 13:20

Copilot started reviewing on behalf of binarywang April 7, 2026 13:20 View session

augmentcode bot reviewed Apr 7, 2026

View reviewed changes

Copilot AI reviewed Apr 7, 2026

View reviewed changes

Copilot started work on behalf of binarywang April 7, 2026 13:31 View session

Copilot AI changed the title ~~Fix V3 payment package field serialized as packageValue instead of WeChat-expected package~~ Fix V3 payment field serialization mismatch with WeChat-expected JSON keys (package, partnerid, prepayid) Apr 7, 2026

Copilot finished work on behalf of binarywang April 7, 2026 13:37

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix V3 payment field serialization mismatch with WeChat-expected JSON keys (`package`, `partnerid`, `prepayid`)#3954

Fix V3 payment field serialization mismatch with WeChat-expected JSON keys (`package`, `partnerid`, `prepayid`)#3954
Copilot wants to merge 4 commits intodevelopfrom
copilot/fix-package-value-issue

Copilot AI commented Apr 7, 2026 •

edited

Loading

Uh oh!

augmentcode bot commented Apr 7, 2026

Uh oh!

augmentcode bot left a comment

Uh oh!

augmentcode bot Apr 7, 2026

Uh oh!

augmentcode bot Apr 7, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 7, 2026

Uh oh!

Copilot AI Apr 7, 2026

Uh oh!

binarywang commented Apr 7, 2026

Uh oh!

Copilot AI commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

Copilot AI commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Result

Uh oh!

augmentcode bot commented Apr 7, 2026

Uh oh!

augmentcode bot left a comment

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

binarywang commented Apr 7, 2026

Uh oh!

Copilot AI commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Apr 7, 2026 •

edited

Loading