AliMPay · Multi-Merchant Payments and Order Operations

AliMPay is for operators and project maintainers managing payment activity across several merchants. It brings payment settings, order follow-up, and everyday overviews into one workspace. The product line extends from an earlier payment component to multi-merchant operations: users can switch between merchants they belong to and inspect the selected merchant’s information and orders without confusing separate businesses. The current workspace is organized around everyday merchant operations.

Prepare and test payment settings

Routine preparation starts with maintaining merchant payment information and QR codes.

• QR code history: The workspace supports updating a payment QR code and reviewing its replacement history to identify the version currently in use.
• Test orders: For integration testing, users can enable an experience page, set its test amount, and provide the resulting entry point. Orders created through this flow are marked as test orders so they can be recognized in everyday lists.

The flow helps inspect an actual integration; a page opening successfully is not evidence that payment processing has been validated.

Investigate an order and its notifications

1. Find the order: Once orders arrive, operators can filter pending, paid, expired, or failed orders, or search by payment flow, order number, product name, or site name.
2. Inspect its details: Counts and amount totals for the matching range help narrow the investigation before opening an order to inspect its requested amount, recorded paid amount, creation time, and payment time.
3. Check notifications: Order details also bring payment events and business notification results together. Users can see when events occurred, whether a notification succeeded, and the attempts made, helping distinguish an order status change from a message delivery problem.

This provides a concrete way to answer questions such as “What stage has this order reached?” Recent activity collects paid orders, failed notifications, and bill-query errors into follow-up entry points. Questions about amounts or which transaction belongs to an order still require checking the actual bill.

Move from trends to individual activity

The overview presents the current merchant’s activity through order-state distribution, payment-flow distribution, daily paid amounts, and changes between time windows, alongside pending-order counts and amounts. Operators can start with trends and move into individual orders to investigate. Demonstration environments may use sample data; operational statistics depend on the merchant’s actual records. The workspace helps make order progress and follow-up work visible.