Conversation
Adds the reference page for paying a Chinese company in USD over the `usd-wire-china` network: the bank contract and its field constraints, the USD 25 minimum, onshore domestic USD versus NRA/OSA over SWIFT with the original invoice up front, the invoice document endpoints, and the rollout state a client reads (`provider_confirmation_pending`, `CHINA_USD_INVOICE_CHANNEL_UNAVAILABLE`). The partner quote/initiate for USD to CN stays closed and the page says so. The page is linked from the API reference index, and the changelog gets a China USD entry. The spec gains `directions` on a payment rail. It was already returned and already filtered discovery, but was undocumented. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… confirmed them The provider corrected the onshore account length: it is 20 digits, not 10, which was a typo in their earlier answer. An NRA or OSA account is that three-character prefix followed by 20 digits and goes over SWIFT only. Domestic USD is not same-day in every case. It usually arrives the same working day when sent before about 3pm Singapore time, and a public holiday in Singapore or China moves it to the next working day. A payment the beneficiary's bank returns is refunded by hand, which can take up to 7 days. The corridor has no per-payment volume limit, so the maximum comes from the executable quote alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…akes exactly 20 digits An NRA/OSA account is its three-letter prefix followed by 20 digits, which the 6–20 bound could not describe. A prefix followed by anything else is saved but refused at execution, like any other unconfirmed format. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The supported-currencies and supported-payment-rails responses do not read a network's `directions`, and rails carry no such property. Say that usd-wire-china is payout-only instead, and remove the claim from the changelog and the Rails schema. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
GET, GET /content and DELETE refuse a request without recipient_destination_id and payout_currency, and a retained invoice is read through its bill_id. The identifier must be the canonical lowercase UUID, the limit is 8 MiB, and a byte conflict returns 409 invoice_document_mismatch. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Preflight and POST /bills refuse an NRA/OSA account without invoice_document_id once the invoice channel is confirmed, and refuse an amount below USD 25 with CHINA_USD_AMOUNT_OUT_OF_RANGE. Both endpoints spell the unconfirmed-account code in upper case. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The payment-rails response has no beneficiary type field, so a client waiting for beneficiary_type on usd-wire-china never gets it. Say the rail's top-level fields are the business schema instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
api-reference/china-usd-payments.md, which covers USD payments to Chinese suppliers:CHINA_USD_ACCOUNT_UNCONFIRMED,CHINA_USD_AMOUNT_OUT_OF_RANGEbelow USD 25,CHINA_USD_INVOICE_CHANNEL_UNAVAILABLE, andINVOICE_DOCUMENT_REQUIREDwhen an NRA/OSA bill names noinvoice_document_id;Before merging
Merging publishes the docs.
/api/v1/bill-payment/*endpoints belong on this page.Checks
redocly lintreports the same findings as onmain.🤖 Generated with Claude Code