Frequently asked questions
Plain-language answers that match what Orion actually does today. Where something is not decided, we say so.
9 questions
What does the customer see?
A hosted checkout showing your business name, order number, items, subtotal, shipping, tax, total and currency, any fees, your refund policy link and support contact, and the available payment methods.
Are customers buying goods or crypto?
Goods. The intended experience is an ordinary purchase of your goods. Orion never secretly turns a card payment into a cryptocurrency purchase. If a provider's model requires the customer to buy crypto, its disclosures and the customer's consent are shown before payment.
Does a customer need a wallet?
Only if they choose to pay directly in USDC. Customers paying by card or Interac do not need a wallet.
Who handles card information?
When live, card details will be entered only into the provider's hosted or tokenized fields. Orion does not collect or store card numbers or security codes. The sandbox does not ask for card details at all — it uses a labelled simulation control.
Which payment methods are available?
In the sandbox: simulated card payments, simulated USDC on simulated test networks, and a simulated Interac e-Transfer with manual confirmation. No live payment method is available.
What appears on the customer's statement?
The statement descriptor is set by the provider and the card networks, usually based on your approved business name. It will be confirmed with the provider before launch.
Why was a payment declined?
Declines come from the provider or card issuer — for example insufficient funds, failed authentication or risk checks. Orion shows the decline code it receives. In the sandbox you can simulate a decline to see how it appears.
When may a merchant fulfil an order?
Only when the payment is marked Succeeded in the portal or API, or you receive a verified payment.succeeded webhook. Never fulfil from a browser redirect, a screenshot, a customer-submitted transaction hash or an authorization that has not been captured.
How are duplicate payments handled?
A paid order cannot start a new checkout. If two payments still succeed for one order, the second is flagged as a duplicate exception so it can be refunded. Repeated or replayed provider events are recognised and ignored.