FOMO Pay IPG PVT Sign-off Tests

Config

FOMO Pay Base URL

MID

TID

PSK

Outlet name

notifyUrl / Callback URL

returnUrl

backUrl

curl uses -u "MID:PSK". Keep the same orderNo / transactionNo when retrying after connection errors.

1. Success Sale Request

Run 1A HOSTED and 1B DIRECT. A unique orderNo is required for every new POST.

1A HOSTED orderNo

1B DIRECT orderNo

Amount

Currency

DIRECT sourceOfFund

DIRECT timeout seconds

1A curl

1A expected JSON

1B curl

1B expected JSON

HTTP 409 means the orderNo was already used.
If transaction creation has a connection error, retry with PUT using the same JSON before creating a new transaction.

2. Success Query Request

orderId

primaryTransactionId

curl

expected JSON

3. Success Refund Request

Refund transactionNo

Refund amount

Refund subject

curl

expected JSON

4. Success Refund Transaction Query

Refund transactionId

Expected subject

curl

expected JSON

5. Success Notify and Query

5A creates a DIRECT sale using your notifyUrl. 5B is the callback body your server should accept and answer with HTTP 200. 5C queries the transaction status using orderId and transactionId.

Notify test orderNo

Notify transactionId

5A sale curl

5A expected JSON

5B notify curl

5B expected JSON

5C query curl

5C expected JSON

notifyUrl must be a valid HTTP or HTTPS URL without userinfo, query, or fragment.
Your server should return HTTP 200 as early as possible, then query the latest FOMO order or transaction status.

6. Failure Cases

6A validates HTTP 4xx handling. 6B is operational: retry after several minutes if a real 5xx persists. 6C expects HTTP 2xx with order status FAIL.

6C fail case orderNo

6C sourceOfFund

6C transactionOptions JSON

6A curl

6A expected JSON

6B curl

6B expected JSON

6C expected JSON

6C curl

Live Result

Browser calls may be blocked by CORS. The curl blocks are the safer copy-paste path for sign-off evidence.

Ready.

Generated curl and expected JSON are ready.