Unique payment code
Make every waiting order expect a different figure, so your statement is readable.
The unique payment code adds or subtracts a small random amount from the order total, so each waiting order expects a figure no other waiting order shares. An order for Rp 150.000 becomes Rp 150.900, and the next one becomes Rp 150.313. That difference is what lets you match a credit in your bank statement to an order.
It is the single most useful setting in the plugin, and everything in Incoming Payments depends on it.
Settings
| Setting | What it does |
|---|---|
| Enable | Switches the code on for every method that does not override it. |
| Mode | Add to the total, or subtract from it. |
| Range | The smallest and largest code. A wider range means fewer collisions. |
| Label | What the code is called at checkout and in emails. |
| Per-method override | Different settings for one method, or none at all for it. |
How the code stays stable
The code is generated once and frozen onto the order. It does not change between the checkout page, the order received page, the confirmation email and the order you open a week later. A code that drifted between those screens would be worse than no code, because the customer would transfer one figure while your records expected another.
Choosing a range
Pick a range wider than the number of orders you expect to have waiting at once. Two waiting orders that land on the same expected figure cannot be told apart from the statement alone, by you or by Pro, and Pro refuses to guess between them rather than settling the wrong one.
Stores whose prices are already odd numbers need less range than stores selling at round prices, where every total ends in three zeros.