Testing Collections

Honeycoin provides separate sandbox workflows for the hosted Universal Payment SDK and the direct collection APIs. Both use configured test values and never send a payment to a live provider, but they do not always expose the same intermediate steps.

Choose Your Integration

Integration	Use it when	Testing guide
Universal Payment SDK	Honeycoin hosts the checkout and handles payment-method forms and challenges	Testing the Universal Payment SDK
Direct collection APIs	Your application calls the mobile money, bank, card, or OPay endpoint directly	Testing Direct Collection APIs

Why the Guides Are Separate

Some values are shared, but the resulting journey can differ by integration:

A hosted card 3DS scenario returns stepRequired: three_ds; the direct card sandbox exposes the same card as a redirect step.
Hosted SDK OTP, PIN, and address-verification challenges use fixed success and failure values inside checkout.
Direct OPay is redirect-first for every configured outcome, while hosted SDK OPay can fail without an additional step.

Use the guide for the integration you are testing instead of assuming that an identical value produces an identical response shape.

Rules Shared by Both Workflows

Authenticate with sandbox credentials and keep production credentials out of test requests.
Use a new externalReference for every attempt.
Treat successful as the only fulfilled state.
Verify the final transaction status through a webhook or transaction-status endpoint before providing value.
Never send real money or real card details to a sandbox flow.

Machine-readable sandbox fixtures are available in manifests/test-data.json.