DreamPay Acumatica operating status — 19 October 2026

ALREADY PUBLISHED / DO NOT RESTART SETUP
Operator-confirmed native set on the existing shared application: Cloud 1.1.0 level110, corrected Workflow1.1.2 level115, Reader1.0.8 level120, SalesOrders0.1.0 level125. Older project-name suffixes are not assembly versions. Preserve existing project identities, endpoint mappings, TEST and ReportCustomize selections.

CURRENT SERVER
Backend0.1.2 corrects an observed Default Invoice/SalesOrder API compatibility issue: mapped SalesOrder.Branch can be omitted. The adapter explicitly requests Document.BranchID and validates the authoritative selector after removing fixed-width whitespace. Missing, wrong or conflicting branch evidence is denied. New order advances remain disabled; existing captured-payment reconciliation and duplicate prevention are retained.
Existing connection: exact tenant CHT Sandbox; endpoint DreamPaySandbox /25.200.001; branch CHT; CAD; DPSBX to TESTCASH; Nuvei Test mode. It is not a production connection. The 24-hour cash-account evidence policy is unchanged.

PRODUCTION IS NOT PROVISIONED
The current backend, provider policy and preserved Reader1.0.8 are deliberately scoped to the CHT test environment. Live capability is not implemented by changing a mode flag. Production requires the exact intended ERP tenant, independently authorized service OAuth/Reader profile, branch/currency/payment method/cash account/posting mapping, merchant identity and actual enabled Nuvei live merchant/site/key references plus authenticated notifications. Do not copy CHT test tokens, accounting mappings or provider credentials into a production profile. No production target or live-provider profile is currently available in this deployment.

BUSINESS USER ACCESS
Use DreamPay Payments for permitted collection actions, DreamPay Viewer for status-only access, effective native screen/action/dialog rights, and existing tenant/branch/customer restrictions. Administrator alone is not a DreamPay payment permission. Internal Authorization Reader is for the service identity, not business users. Refund and Void remain separate privileges. There is no backend tester-username allowlist. Current live business-user role assignments cannot be established or changed through this installation's existing REST contract; native administration access is required.

INTERFACES AND LIMITS
Modern UI order tab was operator-observed. Classic UI tab absence remains unresolved because the actual published ASPX/merge cannot currently be read through native administration. The missing ID attributes in the source XML are not a verified root cause: target-build CstPageData.WriteTitle writes them as descriptive metadata; ExistingControlBinding resolves the ParentId.
Native0.1.1 status/access correction is compiled and prepared separately, not published: explains eligibility locally, adds read-only status actions to specified nonpayable states and prevents generating an advance outside Open/Awaiting Payment. No role/tenant/approval restrictions are removed.
SO000039 remains Pending Approval. Do not change the approval map, approve it merely to expose a button, or alter its financial data.

EVIDENCE AND UNSUPPORTED BEHAVIOR
Existing invoice000042/payment000034/posted GL000076 remain preserved. Full quotation/order/prepayment/shipment/invoice/remainder financial execution is unverified. No demonstration charge, link, invoice or accounting document was created in this completion pass. HTTP200 and published projects are not payment-readiness evidence.
Order advance refunds/voids, split or combined invoices, FX, automatic cancellation/uncertain-charge release and unsupported adjustment histories remain unavailable/review-required. Existing invoice reversal support is narrowly scoped; do not advertise arbitrary refunds or voids.

REMAINING ACCESS
A controllable, authorized Acumatica native administrator session or supported equivalent is needed to inspect the actual Classic merge, publish the prepared correction into the same existing project, inventory/evaluate business-user effective rights, and read the saved native Workflow state. Do not restart installation or repeat screenshot exercises. No new transaction is needed to resolve these configuration/access blockers.
