Sources and Open Items
Before integration and launch, use the implementation limits and open-item checklist below to confirm the capabilities enabled in your target environment. See Testing & Troubleshooting for acceptance scenarios.
Documentation Sources
This page retains the verification record from the original Singapore integration guide, including the MIS Dedicated Payment Device API Reference (revision 407 read for the original guide) and the local code revisions below.
The supplied Stripe documentation-design research informed the task-first structure, API reference, recovery paths and evidence-based acceptance tests. Stripe API or idempotency behavior is not an AiMT contract.
The revisions and code locations below come from the original verification record. Restoring this documentation does not mean these repositories have been reviewed again, that the same revisions are deployed, or that real device/channel acceptance tests have passed.
Code Verification Scope
Code Locations Recorded in the Original Guide
- upay-api:
internal/router/router.go:129,146;internal/auth/auth.go:113,218,343;internal/router/admin/admin.go:154. - app-push-service:
MisTradePushController.java:45,161;MisPushApiExceptionEnumV2.java;MisServiceImpl.java:177;AllinpayServices.java:35,114. - upay-frontend-proxy:
MisPushController.java:23;MisPushServiceImpl.java:109,166,273. - upay-gateway:
UpayServiceImpl.java:531,1397,1410,1529;DataRepository.java:142;RefundProcessor.java:484,787,916;ClientNotifier.java:85,276,300;TransactionResponder.java:93,133. - Additional RSA encoding source:
mpay-sdk-homebrew/RsaSignature.java:68,199.
Because the additional RSA source and gateway dependency differ, complete callback verification using authentic signature samples from the target environment.
Reconciled Differences
Known Implementation Limits
- Query route: Ingress registers
/mis/query, but the frontend-proxy checked for the original guide has no corresponding implementation. This documentation therefore uses the verified/upay/v2/query. - Cancellation notification coverage: Some Allinpay/KPay forwarding paths do not pass through
tradePush.cancel_notify_url; cancellation notifications are not promised for every device. Verify cancellation delivery on the target device and route, and use queries to confirm final outcomes.
Confirm Before Launch
Original Guide Coverage
On 2026-11-12, both language versions were compared with the original HTML guide. The check covered its 26 anchored sections, solution overview, 26 tables (197 rows including headers), and 34 code/example blocks per language, including the downloadable Python source. No API chapter, parameter table or code example was missing. Existing onboarding diagrams retain the three phases and eight steps.
Restored the source/verification links in the capability and callback examples. Converted the text-only payment workflow and order-state path to Mermaid, retaining acceptance-versus-payment distinctions, query recovery and refund boundaries. This is a documentation comparison, not a new verification of backend code or deployed capabilities.
Revision History
-
2026-10-22, original revision: Added first-payment guidance, four-layer result interpretation, recovery, errors and acceptance tests. Corrected retry IDs, refund identity, raw notification verification/acknowledgment/deduplication, check-in signing and refund/shift limits. The original guide retained existing anchors and bilingual switching. Documentation only; no API behavior changed.
-
2026-11-11, Markdown restoration: Restored sources, code verification scope, reconciled differences, implementation limits and open items. Retained this page's
sourcesanchor and provided English and Chinese versions. No target-environment revalidation or API behavior change. -
2026-11-12, source comparison and diagrams: Checked coverage against the supplied original URL, restored source links, and added Mermaid payment and order-state diagrams in English and Chinese.
