docs: document China's AliPay and WeChat Pay payout rails - #841
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
✱ Stainless preview builds for gridThis PR will update the cli go kotlin openapi php python ruby typescript ✅ grid-ruby studio · code
|
Co-Authored-By: pengying <pengying@users.noreply.github.com> Co-Authored-By: Jason Wang <jason@lightspark.com> Co-Authored-By: Dan Bonato <dan@lightspark.com>
9e08d7f to
b8c6296
Compare
Greptile SummaryThe PR documents the distinct wallet and bank-transfer payout options available for China and aligns the CNY examples with their beneficiary requirements.
Confidence Score: 5/5The PR appears safe to merge, with the documentation, examples, source schema description, and generated bundles aligned. No concrete changed-code defect remains; the exact wallet identifier is explicitly documented, the examples match the described beneficiary constraints, and the generated OpenAPI artifacts mirror the source change.
|
| Filename | Overview |
|---|---|
| mintlify/snippets/country-support.mdx | Adds China’s consumer wallet rails and clearly distinguishes their beneficiary scope from business-only bank transfers. |
| mintlify/snippets/external-accounts.mdx | Corrects the AliPay identifier, changes the bank example to a business beneficiary, and documents exact wallet-selection values. |
| openapi/components/schemas/common/CnyAccountInfoBase.yaml | Clarifies the rail-specific fields and beneficiary constraints without changing the serialized schema shape. |
| openapi.yaml | Correctly reflects the regenerated CNY account-description change from the modular source. |
| mintlify/openapi.yaml | Remains synchronized with the regenerated root OpenAPI bundle. |
Reviews (1): Last reviewed commit: "docs: document China's AliPay and WeChat..." | Re-trigger Greptile

Summary
The country table listed China as
Bank Transferonly. That was wrong in both directions: it omitted the AliPay / WeChat Pay wallet rail that consumer payouts actually use, and it implied the bank rail works for paying individuals when that rail is business-to-business only.What changed
AliPayWeChat PayBank Transfer, with a note that the wallets serve individual beneficiaries and the bank rail is B2B-only."bankName": "Alipay"and anINDIVIDUALbeneficiary on the bank-transfer payload. The wallet name is now the exact spelling the payer lookup matches, and the bank-transfer example uses aBUSINESSbeneficiary (legalName+registrationNumber) to match the rail.CnyAccountInfoBasedescription spells out the per-rail constraint rather than just listing required fields.UnionPay is deliberately left out — it is not an enabled payout rail for this corridor today, so documenting it would promise something the API cannot route.
Verified against live configuration
The claims above were checked against the live payout configuration rather than assumed:
AliPayandWechatPay— one word, no space. A wallet is selected by matching the payeebankNameagainst that registered name, so a caller sending"WeChat Pay"would not resolve. That is why the note pins the accepted spellings.Changes: 5 files
mintlify/snippets/country-support.mdx— China rails row + rail/beneficiary notemintlify/snippets/external-accounts.mdx— China tab: wallet spelling, B2B bank example, expanded noteopenapi/components/schemas/common/CnyAccountInfoBase.yaml— per-rail descriptionopenapi.yaml,mintlify/openapi.yaml— regenerated viamake buildTest plan
make lint→ 0 errors, and the warning/info counts are byte-identical tomain(662 problems both before and after), so this adds no new lint debt.@mdx-js/mdx— all three parse, confirming the added<Note>doesn't break the page.accountNumber+BUSINESS; wallet →phoneNumber+AliPay).bolt-adversarial-review→ no P0/P1/P2 findings.Public
Documents China's AliPay and WeChat Pay payout rails and clarifies that the CNY bank rail is business-to-business.