Statuses
The statuses of merchants, projects, orders and transactions, how they change, and what each one means for you as the operator.
Merchants, projects, orders and transactions each have a status. The merchant and project statuses are yours to manage: they decide whether a business can log in and take payments. The order and transaction statuses tell you, and your merchants, what happened to a payment.
You see every status in the Admin portal: on the Details page of a merchant, on the General tab of a project, and on the detail pages of orders and transactions, with a timeline of every change.
Merchant statuses
| Status | Meaning | Logins and payments |
|---|---|---|
pending | Created, not live yet. A new merchant starts here while you board it. | Activate the merchant before you test it. |
active | Live. | Users log in, projects take payments. |
ending | The end date of the merchant's main contract has passed, and the ending period runs. | The projects can't start new payments. When you choose ending, the Admin portal warns that users lose access to the Merchant portal and the API key stops working. Ask your Ginger contact what still works in the ending period. |
ended | Closed at the end of the ending period. Nothing can be changed anymore. | Users and API keys can't log in. |
inactive | Removed, for example because the merchant's application was rejected. Deleting a merchant sets this status. | Users and API keys can't log in. |
Ginger moves a merchant from active to ending when the end date of its main contract has passed, and from ending to ended when the ending period is over. You set the other statuses yourself, with Edit on the merchant's Details page.
Ended is permanent
A merchant in ended can't be changed anymore, not even by you. Use inactive if you may need the merchant again: ending moves on to ended by itself when the ending period is over.
Project statuses
| Status | Meaning |
|---|---|
active-testing | Test mode. Orders get the is-test flag and no real money moves. |
active-production | Live mode. Real payments. |
inactive | Removed. Deleting a project sets this status, and its API key stops working. |
A merchant has a test project and a live project for each webshop or app: you create the test project when you board the merchant, and the live project when it goes live. Don't switch a test project to active-production: create the live project instead. Automatic merchant boarding at Silverflow only runs for projects in active-testing or active-production.
Order statuses
An order is what your merchant's customer buys. Its status tells your merchant whether to deliver. The meaning of each status, and the typical flow, are in Order and transaction statuses in the payment acceptance docs. Point your merchants there.
| Status | Final | What it tells you |
|---|---|---|
new | No | Created, the customer hasn't started paying. |
processing | No | A payment is underway. An attempt that stalls stays here until the order expires. |
completed | Yes | Paid. The merchant can deliver. |
cancelled | Yes | Cancelled by the customer or the merchant. |
expired | Yes | Not paid in time. |
error | Yes | The payment was declined or failed. Check the transaction for the reason. |
The order status follows from the statuses of its transactions, with these exceptions:
- An order without transactions goes from
newtoexpired. - When the completed amount reaches the order amount, the order goes to
completed. - An order without a completed transaction stays
processinguntil it expires.
Linked orders and flags
A capture, a void, a refund and a chargeback each create their own order and transaction, linked to the original one. On the original order, flags sum up its history. The ones you see most:
| Flag | Meaning |
|---|---|
is-test | Created on a project in active-testing. |
has-captures, has-voids, has-refunds, has-chargebacks | The order has linked capture, void, refund or chargeback orders. |
is-capture, is-void, is-refund, is-chargeback | The order itself is one of these. |
from-payment-link | Created from a payment link. |
Transaction statuses
A transaction is one payment attempt on an order, with one payment method. Most orders have one; a customer who gives up on one method and pays with another creates two. When an order isn't completed, its transactions tell you why.
| Status | Meaning | Final |
|---|---|---|
new | Created, the customer isn't at the payment method yet. | No |
pending | Waiting for the customer or their bank, for example for 3-D Secure authentication. Some payment methods skip it. | No |
processing | Being processed by the processor. | No |
accepted | The payment succeeded. For a card authorisation, the amount is reserved and can be captured. | No |
captured | An authorised amount was captured. | Yes |
completed | The payment is posted on the merchant's balance. | Yes |
cancelled | The customer or the merchant cancelled the attempt. | Yes |
expired | The attempt, or the authorisation, ran out of time. | Yes, with exceptions |
error | Declined, or failed for technical reasons. The reason field says why. | Yes, with exceptions |
The rules behind the diagram:
- A transaction in
neworpendingexpires automatically after the expiration period, and can be cancelled. completedandcancellednever change.accepted,errorandexpiredonly change tocompleted,cancelledorcaptured, andacceptedcan also expire.- When an authorisation is captured, the original transaction stays
accepted: the capture order gets its own transaction that completes.
Next steps
- Merchant hierarchy: merchants, projects and permissions.
- Board a merchant: from
pendingtoactive. - Tour the portals: where you find orders and transactions.