Skip to content

Mock Channel: FAQ and Troubleshooting ​

Updated: 11/10/26, 10:51:10 AM

Callbacks Do Not Reach the Main App ​

Check three things in order: whether Admin Panel "Platform Configuration → Endpoint Configuration" is configured and reachable from the machine running mock; whether the callback records in the order detail were sent and what HTTP status they returned; whether the main app resolves the callback address as a public domain (local integration needs a hosts entry pointing back to the local machine).

Order Fails with "Product Strategy Does Not Exist" ​

The mock orchestration module is not wired when the main app starts in PROD mode, so routing to mock always fails with this error. Restart in dev mode, or switch the app routing to a real channel.

Mock Channel Missing from Routing Candidates ​

Two possibilities: the wrong data set (the clean data set data.sql has no mock channel master data — switch to data-demo.sql); or capability master data rows are missing, so candidate validation on save filtered out that payment method.

Confirmation Page Does Not Open / Phone Scan Returns 404 ​

The confirmation page address is generated by the mock service itself (http://{mock-host}:10400/#/pay/...). If the scanned address points at 127.0.0.1, the phone can never open it — make mock listen on a LAN address, or open the confirmation page on the computer and simulate separately on the phone.

Rules Do Not Take Effect ​

The decision chain has four layers: order manual override → merchant level → ISV level → transaction type default. The rule you changed may be overridden by a higher layer. Check whether subject profiles hold per-subject overrides, and whether the amount last digit matches the split payment rule.

Aggregate Payment Pushed to Success Is Rejected (40404) ​

Aggregate orders pushed to success must carry an actual wallet. Only clicking one of the four wallet buttons on the confirmation page writes actual_provider; if you push the final state through the API directly, include the wallet field explicitly. Failures and pending states do not require a wallet.

Data Disappeared / Want to Clear and Start Over ​

All data lives in data/mock-channel.db (WAL mode adds -wal and -shm files) and does not reset on restart. The console's "Clear All Data" clears orders / refunds / split payments / callbacks only, leaving profiles and rules untouched; to reset profiles too, delete all three files and restart — the built-in seeds are recreated.

Console UI Changes Do Not Take Effect ​

The production form serves the build output from the backend static directory. After changes you must run cd ui && pnpm build again and commit the output, otherwise the changes exist only in the dev server (10500).

Mock Channel Starts but Orders Do Nothing ​

First confirm the order actually routed to mock: check the channel sub-app log for outbound requests, and the mock console order list for a new order. If the order exists but its state does not move, check whether the confirmation page was clicked; if no order exists, the routing or channel merchant number is not paired.

Should It Be Installed in Production? ​

No. The production deployment checklist does not include the Mock Channel, and the main app does not wire the mock module. To demo for customers, prepare a separate demo environment or use the Ops Panel's demo mode.