Sandbox Testing - OneClickDz Flexy API

How the sandbox works

A sandbox key uses the same base URL, routes, envelope, statuses and polling as production. The differences:

No biller is contacted and no money moves.
The outcome is chosen by the account identifier you send (tables below). Any other identifier returns one bill of 500.00 DZD and a successful payment.
Discovery completes in about 0.2 s and payment in about 0.5 s, so your poller still has to handle PENDING and PROCESSING.
GET /v3/bills/partners reports every biller ACTIVE.
Receipts are PNG images.
Sandbox and production transactions are fully separate. A sandbox key never sees a production transaction, and vice versa.

Confirm which environment a key belongs to with Validate Access Token.

Test accounts

ADE

account: { "electronic_payment_key": "<value>" }

`electronic_payment_key`	Discovery	Payment
`0123456789012345678901234`	1 bill, 443.39 DZD	`SUCCESS`
`0123456789012340000000001`	1 bill, 320.00 DZD	`SUCCESS`
`0123456789012340000000002`	`READY`, `bills: []`	—
`0123456789012341111111111`	`READY`, `bills: []`	—
`0123456789012340000000004`	1 bill, 400.00 DZD	`FAILED`, `PAYMENT_DECLINED`
`0123456789012340000000005`	1 bill, 550.00 DZD	`REFUNDED`, `PAYMENT_DECLINED`
`0001234567890000000000000`	1 bill, 600.00 DZD	`REFUNDED`, `PAYMENT_DECLINED`
`0123456789012340000000006`	`409 BILL_ALREADY_PAID`	—
`0123456789012347777777777`	`409 BILL_ALREADY_PAID`	—
`0123456789012345005005005`	`503 PARTNER_UNAVAILABLE`	—
`abc0000000000000000000000`	`400 INVALID_ACCOUNT`	—

SONELGAZ

account: { "sonelgaz": { "invoice_number": "<value>", "amount_without_stamp": "1200.00", "ebb_key": "123456" } } — the outcome depends on invoice_number; the other two fields only need to be present.

`invoice_number`	Discovery	Payment
`9876543210`	2 bills, 1200.00 and 850.00 DZD	`SUCCESS`
`4004004004`	1 bill, 500.00 DZD	`FAILED`, `PAYMENT_DECLINED`
`6006006006`	1 bill, 900.00 DZD	`UNKNOWN` for about 60 s, then `REFUNDED`
`0000000003`	`READY`, `bills: []`	—

SEAAL

account: { "seaal": { "code_client": "<value>", "code_contrat": "446563" } } — the outcome depends on code_client; code_contrat only needs to be 2 to 10 digits.

`code_client`	Discovery	Payment
`100001`	5 quarterly bills (456.33 × 3, 327.00 × 2)	`SUCCESS` (test `billIds` here)
`100002`	1 bill, 512.75 DZD	`SUCCESS`
`100003`	`FAILED`, `BILL_ALREADY_PAID`	—
`100004`	1 bill, 389.10 DZD	`FAILED`, `PAYMENT_DECLINED`
`100005`	`FAILED`, `INVALID_ACCOUNT`	—

AADL

account: { "aadl": { "codeloc": "<value>" } }

`codeloc`	Discovery	Payment
`1112223334`	1 notice, 5400.00 DZD, with `breakdown`	`SUCCESS`
`2223334445`	1 notice, 12000.00 DZD, with `breakdown` showing 2 unpaid periods	`SUCCESS`
`3334445556`	`READY`, `bills: []`	—
`4445556667`	`FAILED`, `BILL_ALREADY_PAID`	—

The AADL notice endpoint (/avis) is not available in the sandbox.

SEOR

account: { "seor": { "contrat": "100001", "facture": "<value>" } } — the outcome depends on facture; contrat only needs to be 1 to 6 digits.

`facture`	Discovery	Payment
`00102026S000000001`	1 bill, 1003.20 DZD, period `2/2026`	`SUCCESS`
`00102026S000000002`	`FAILED`, `BILL_ALREADY_PAID`	—
`00102026S000000003`	`FAILED`, `INVALID_ACCOUNT`	—
`00102026S000000004`	1 bill, 850.40 DZD	`UNKNOWN`, never refunded automatically

Algérie Télécom

account: { "phone_number": "<value>" }

`phone_number`	Discovery	Payment
`023456789`	1 bill, 300.00 DZD	`SUCCESS`

Errors you can trigger

How	Result
Omit the `X-Access-Token` header	`401 MISSING_ACCESS_TOKEN`
Send a wrong key	`401 INVALID_ACCESS_TOKEN`
Send the same `ref` twice to `discover` for the same partner	`403 DUPLICATED_REF`
Send two identifiers in `account`	`400 ERR_VALIDATION`
Reuse the discovery `ref` on `pay`	`403 DUPLICATED_REF`
Pay a transaction that is not `READY` (still `PENDING`, or already paid)	`404 NOT_FOUND`
Pay with a `billId` that is not in the transaction’s `bills[]`	`404 NOT_FOUND`

A complete sandbox run

# 1. Discover
curl -X POST https://api.oneclickdz.com/v3/bills/discover \
  -H "X-Access-Token: $ONECLICKDZ_SANDBOX_API_KEY" -H "Content-Type: application/json" \
  -d '{"partner":"SONELGAZ","account":{"sonelgaz":{"invoice_number":"9876543210","amount_without_stamp":"1200.00","ebb_key":"123456"}},"ref":"test-0001"}'

# 2. Read the bills (repeat until READY)
curl https://api.oneclickdz.com/v3/bills/transactions/{transactionId} \
  -H "X-Access-Token: $ONECLICKDZ_SANDBOX_API_KEY"

# 3. Pay one of the bills
curl -X POST https://api.oneclickdz.com/v3/bills/pay \
  -H "X-Access-Token: $ONECLICKDZ_SANDBOX_API_KEY" -H "Content-Type: application/json" \
  -d '{"transactionId":"{transactionId}","billId":"{billId}","ref":"test-0001-pay"}'

# 4. Confirm (repeat until SUCCESS / FAILED / REFUNDED)
curl https://api.oneclickdz.com/v3/bills/transactions/{transactionId} \
  -H "X-Access-Token: $ONECLICKDZ_SANDBOX_API_KEY"

# 5. Receipt
curl https://api.oneclickdz.com/v3/bills/transactions/{transactionId}/receipt \
  -H "X-Access-Token: $ONECLICKDZ_SANDBOX_API_KEY" --output receipt.png

Before going live

Your poller handles every status, including UNKNOWN (SONELGAZ 6006006006).
A FAILED or REFUNDED payment does not leave a charge on your customer.
A 409, 403 or timeout never triggers a second pay.
Every pay uses a new ref.
Multi-bill orders show selectedBills correctly (SEAAL 100001).
Receipts are stored with operationId.
The production key is loaded from configuration, never from code.

​How the sandbox works

​Test accounts

​ADE

​SONELGAZ

​SEAAL

​AADL

​SEOR

​Algérie Télécom

​Errors you can trigger

​A complete sandbox run

​Before going live