What the documents look like
In the foreign-exchange settlement and trade directory category, the shared-access step handles a defined set of materials: foreign-exchange receipt advices, trade contracts, invoices, and foreign-exchange business registration records. The fields that matter for reconciliation are the identity of the parties (whether payer and payee match), amount and currency, date range, and the explanation of trade background. This category does not review a full set of letter-of-credit documents; the focus is the authenticity of foreign-exchange funds and the underlying trade. Practitioners include foreign-trade finance staff, bank account managers, and foreign-exchange specialists. Errors can lead to bank rejection, abnormal foreign-exchange classification, or funds that cannot be credited. Data updates occur per transaction and monthly, so conversation records and quoted fragments carried by a share link need to align with the time boundary of an individual transaction.
Constraints at the shared access step
The no-login window is created from the publishing channel and the system-generated full link is copied. The link identifier itself does not constitute business authorization. The identity verification feature is limited to the commercial edition and uses the official interface return of a success status and a uid to decide whether the user may continue. An anonymous localId depends on the same device and same browser; cross-device records require separate identity and session management. Conversation record retrieval is limited to 20 records within the past 30 days. These constraints directly affect how the authorization boundary is designed when a share link is embedded into an external system for order fulfillment and after-sales questions.
Hypothetical paper exercise sample: a foreign-trade enterprise finance staff member receives an export receipt. The payee entity is Company A, the payer is Company B, the amount is USD 50,000, the date is 15 March 2025, the trade contract number is HT-2025-0315, and the invoice number is INV-2025-0315. The staff member plans to share the receipt reconciliation result with a bank account manager through a no-login share link. The proposed sentence is: "The receiving entity for this receipt matches the contract seller; please confirm that settlement can proceed." The pending request is: embed this share link into the bank's internal system with authToken=userid12345 attached.
Configuration and implementation checks
| Configuration item | Relevant setting or check on this page | Hypothetical trial starting point and comparison method |
|---|---|---|
| Identity verification root address | Enter the POST root address; triggers init, start, and finish interfaces | This trial starts from https://example.com, compared with the root address format after removing /shareAuth/finish in the official example |
| authToken concatenation | Add an extra query parameter to the share link | This trial starts from authToken=userid12345, coexisting with the existing shareId parameter; compare whether the concatenated full link opens |
| uid return format | Interface returns success as true and data.uid as a string without specified characters | This trial starts from uid=user1, compared with the official format requirement of no more than 255 bytes |
| Expiration time | Set according to the scope of use; verify the actual edition | This trial starts from 15 April 2025, compared with the sample date of 15 March 2025 to confirm coverage of the business period |
| Point cap | Check the usage limit and cost attribution of the share entry | This trial starts from 1000 points, compared with the official condition that some parameters are edition-restricted |
| Conversation record boundary | Anonymous localId depends on the same device and same browser | This trial starts from access on the same browser, compared with a cross-device scenario to confirm the record retrieval scope |
Three common errors
- Treating the link identifier as business authorization. The no-login window link only provides access to the application; it does not confirm the receiving entity, amount, or trade background. Input is the share link; the comparison object is the business authorization document; the observable result is that the link opens but cannot replace bank review.
- Treating a success of true from identity verification as completion of business approval. Identity verification only decides whether the user may continue; uid is used to retrieve and save conversation records. Input is the authentication interface response; the comparison object is the business approval status; the observable result is that the user can continue the conversation while the approval status remains unchanged.
- Treating the anonymous localId record retrieval scope as complete session management. The official description allows retrieval of only 20 records within the past 30 days and depends on the same device and same browser. Input is a cross-device access request; the comparison object is the record retrieval condition; the observable result is that records may be lost and identity and session management must be designed separately.
How to verify the setup
- Use the proposed sentence from the hypothetical sample, "The receiving entity for this receipt matches the contract seller; please confirm that settlement can proceed," and enter it into the share link conversation. The comparison object is the payee Company A, payer Company B, contract number HT-2025-0315, and invoice number INV-2025-0315 in the sample materials. The observable result: if the conversation returns content consistent with the sample materials, the quoted fragment display is normal; if the returned content is missing the entity or amount, record the gap.
- Use the hypothetical request "embed this share link into the bank's internal system with authToken=userid12345 attached" and enter it at the identity verification root address. The comparison object is the success field and uid field in the official interface return format. The observable result: if success is true and the uid format meets the requirement, authentication passes; if success is not true or uid is missing, record as pending verification.
- Use the hypothetical sample date range of 15 March 2025 to 15 April 2025 and enter it into the conversation record retrieval scenario. The comparison object is the official condition of 20 records within the past 30 days. The observable result: if the record retrieval scope covers the sample dates, the boundary condition is met; if it exceeds the range, record as unsupported.