Troubleshooting
Diagnose before you guess, then jump to the symptom you are actually seeing.
Most integration problems look like a mystery for about two minutes, and then turn out to be one of a dozen things. This section is organised the way you arrive: by what you are seeing, not by what it is called.
Before you open any page below, collect three things. With them, almost every question answers itself, and without them support cannot help you either.
| What | Where it is | Why it settles the question |
|---|---|---|
| The payment id | transaction.id on the create response, trx_… | Names the object on Wajub's side |
| The request id | X-Request-Id on any response | Names the exact call in Wajub's logs |
| The environment | The key prefix, pk_test. or pk. | Sandbox and live are different databases |
That last row is the single most common false alarm. A sandbox object is invisible to a live key and
the other way round, and the id says which: everything created in sandbox carries test_ after its
prefix, as in trx_test_CSUGajfv9xh0XQ5wu2lx.
Start in Konsole
Konsole shows the request you actually sent, the response Wajub actually returned, which provider was picked, and whether the webhook was delivered. Reading it takes less time than reasoning about what your code should have done.
| You want to know | Open |
|---|---|
| What my code sent and got back | API Logs |
| Why this provider was chosen | Routing Log |
| Whether my endpoint answered | Webhook Tester |
| What is happening right now | Event Stream |
Go to your symptom
Related pages
- PaymentsStuck on pending, failed without explanation, charged twice, 404 on an id.
- WebhooksNothing arrives, the signature never verifies, the same event three times.
- TransfersRefused with 406, failed on send, throttled in a payout loop.
- Keys & accessEvery 401, 403 and 406, and the CORS error that is not one.
When it is not you
Platform incidents, degradations and maintenance windows are published on status.wajub.com. Check it before you spend an hour on a failure rate that started at the same minute for everyone.
When none of this helps
Write to support@wajub.com with the three things from the table at the top, plus what you expected to happen. A request id turns a conversation that takes two days into one that takes ten minutes, because it points at the exact call rather than at a description of it.