Skip to content
Last updated

Testing in production

Omno provides a single production environment. You test by making real API calls against test providers (test PSPs) that Omno configures on your production account.

  • Test transactions are not charged or billed.
  • Test providers return predefined statuses and controlled responses so you can simulate each outcome.
  • When testing is finished, Omno removes the test providers from your configuration.

Request a test setup

Contact Omno at support@omno.com to have test providers configured on your account. In the dashboard the test providers appear under Payment Providers → Add Provider → Authorize (dashboard labels may read "Fake …"):

  • Fake Card Pay-In
  • Fake APM Pay-In
  • Fake Card Pay-Out
  • Fake APM Pay-Out

After authorizing each, make sure it is added to your Router and active.

Identify test transactions

A transaction processed by a test provider has merchantPspId / processorPspId equal to the test-provider ID Omno gave you. Check this field (via the webhook payload or a GET on the transaction) before touching balances.

⚠️ Warning: Never credit or debit real player balances for transactions processed by a test provider.

Simulate outcomes

The test provider decides the outcome from a controlled input: the CVC for cards, or a 3-digit value in the recipient field for APMs.

Cards (Cashier, Single Payment, Hosted Payment Fields, Payment Page)

Use these test cards (test provider only):

PurposeCard numberExpiryCVC
Success453914880343646712/29123
Failure (before provider)601111111111111712/29123
3DS challenge37828224631000512/29123

Cardholder name can be any value. For 3DS, you're taken to a simulated provider page where you choose the final outcome.

Card decline simulation by CVC:

CVCResult
001General card decline
004Card expired
005Card inactive or blocked
011Insufficient funds
013Invalid card number
015CVV check failed
026Transaction marked as fraud
033Provider timeout
034Provider rejected request
040Service unavailable

The test APM provider uses the same 3-digit codes as card declines, but you enter the value in the recipient field instead of the CVC.

Payout confirm / reject

Payout decline simulation:

CodeResult
002Transaction not allowed
004Card expired
005Card inactive
011Insufficient funds
013Invalid card number
016Invalid amount or currency
026Marked as fraud
033Transaction timeout
034Rejected by provider
040Service unavailable

For payouts that require manual approval, exercise both confirm and reject.

Outcome coverage

OutcomeHow to simulate
SuccessSuccess card / valid input.
Decline (by provider)CVC / recipient decline codes above.
Failure (before provider)Failure card, or a routing/provider restriction.
TimeoutCard CVC 033, or payout code 033.
3DS (card)Card 378282246310005.

ℹ️ Note: Failures occur before the provider (routing or provider restrictions); declines are returned by the provider; success depends on valid input and routing eligibility.

Build it →