Integration

One API for Africa's card stack

REST API, clear docs, and first live transaction in under a week.

What you integrate

enza API surface

The enza API covers card acceptance, fraud scoring, clearing, and settlement through one endpoint set. Your payments team uses one authentication credential and one webhook for transaction events.

  • One API key for card operations
  • One webhook for transaction events
  • OpenAPI spec in the dashboard

API docs

A small API surface

Four core endpoints. Clear request/response contracts. OpenAPI spec available from the dashboard.

POST /v1/accept Submit a card transaction for acceptance and fraud scoring
POST /v1/clear Start clearing for an accepted transaction
POST /v1/settle Send settlement instructions to your account
GET /v1/status/{transaction_id} Get the current status of any transaction

Integration schedule

API key to production in one sprint

1

Get access

Request access and get sandbox credentials within one business day.

2

Sandbox test

Run sandbox transactions against real scheme simulators. Validate acceptance, fraud scoring, and clearing flows.

3

Set up

Set fraud thresholds and webhook endpoints in the dashboard. Choose reconciliation export preferences.

4

Launch

Submit for production review. Our integration team reviews and approves within 3 business days.

Your integration engineer is close by

Every enza account has a named integration contact, with direct access to the engineer who knows the API, not a ticket queue.

Request integration guide