Nexus warns readers against combining vendor payments now

The payment screen now carries a warning against combining multiple orders into a single deposit, whether the orders are with the same vendor or different ones.

Combining payments used to be a shortcut some readers reached for. They had two orders in checkout at the same time, they added the two totals together in their head, and they sent one lump sum from their sending wallet expecting the market to split it. That shortcut has always been fragile. The market is now saying so out loud.

How it read before

The old payment page did not warn about combining. Nothing on the screen said "one deposit per order". If a reader combined two orders in one send, sometimes the market allocated the money to one of the orders and left the other short. Sometimes it split and both cleared. The outcome depended on invisible allocation rules that nobody was in a position to predict from the reader side.

When it went wrong, the fix landed in support. The reader would explain that they had sent one lump sum for two orders and ask for the allocation to be corrected. Staff had to look at the deposit transaction, the order IDs, and the timing to piece together what the reader had intended. It was avoidable work.

How it reads now

The payment screen now shows a warning box below the amount that says, in plain terms, that combining vendor payments into a single deposit is not supported and that each order should be paid on its own. The wording is neutral and the box is set apart from the rest of the copy so it is hard to skim past even for a reader who is scanning listings fast.

The invoice amount and the address on the pay screen are per-order. Two open orders means two invoices. The warning is a reminder of what the pay screen already shows, but the reminder is now printed rather than assumed.

Why this probably shifted

The most likely reading is a support-load answer. Every mis-allocated combined deposit is a ticket. Every one of them is a task that takes a person a chunk of time to reconstruct. Adding a warning is the cheapest possible intervention that shifts the failure mode out of the market and back onto the reader.

A related reading is that per-order accounting is cleaner for the market and for the vendor. A single deposit paying one invoice is a clean row. A single deposit paying part of two invoices requires bookkeeping that has to be right every time or somebody is left out of pocket. The change removes the ambiguous case.

What to change on your side

Pay each order on its own. Do not add invoice amounts together, even if the orders share a vendor. If you have two open orders and one wallet, send each amount separately, ideally in two separate transactions.

• One invoice, one send. If you have two invoices, do it twice.
• Do not send an amount that is a sum of two invoices; the pay screen will not know what to do with it.
• If you have already combined by accident, write to support with the transaction ID, both order IDs, and the amounts, before you message support too late.
• If a vendor is asking you to combine because it is easier for them, cross-check the ask against the refund policy in the listing before doing anything they suggest.

It helps to think about the pay screen as a bill from a specific vendor for a specific order. You would not pay two separate restaurant bills with one card swipe and expect the restaurant to figure it out. The invoices work the same way.

What this entry is not claiming

This entry is not claiming that combined deposits never landed in the past, that support cannot fix a mis-allocation, or that the warning box is impossible to overlook. It is claiming that the copy on the payment screen has been changed to state the constraint openly, and that the constraint has always been the safer read of how the pay screen actually works.