Payment gateways

• Wave (WAVEXOF), stored for Senegal/XOF flows.
• Orange Money (ORANGEXOF), stored for Senegal/XOF flows.
• M-Pesa (MPESAKES), using Safaricom Daraja credentials for Kenya.

1. 1Obtain a Wave Business API key from the provider.
2. 2In Payment Gateways, enter the API key in the Wave card.
3. 3Choose Test Connection and wait for a successful result.
4. 4Choose Save Key. Confirm the provider appears as active in credential history.

Wave API key: wave_test_example_7f4a2c9d

1. 1Obtain the Merchant Key and Public Key shown by your Orange Money provider account.
2. 2Enter both values in the Orange Money card.
3. 3Choose Test Connection, correct any error, then choose Save Keys.
4. 4Confirm Orange Money appears as connected.

Merchant Key: om_test_merchant_example
Public Key:   om_test_public_example

1. 1Obtain your Consumer Key and Consumer Secret from Safaricom Daraja.
2. 2Enter Merchant Name and CPI (business shortcode) as issued for your merchant account.
3. 3Choose Test Connection, then save the keys after a successful test.
4. 4Confirm M-Pesa appears as connected and note the last-tested time.

Consumer Key:    daraja_test_consumer_example
Consumer Secret: daraja_test_secret_example
Merchant Name:   Example Store
CPI:             123456

EasyMoPay stores the credential set entered in each gateway card; it does not expose a separate environment selector. Use provider-issued sandbox credentials during testing. When ready, replace them with production credentials, retest, save, and complete a controlled live transaction.

Gateway credentials are encrypted at rest with authenticated encryption before database storage. The dashboard masks saved values. Never use real keys in documentation, chat, logs, screenshots, or source control.

After at least one active credential exists, Settings displays a Default Gateway control. Select an available provider and save it. Only active, configured gateways appear in this list.