Resources
Developer support
Integration questions, unexpected errors and access requests all go through Century support inside the app.
Open a ticket
Signed-in users can start a support conversation from the support desk, attach the affected transaction, and escalate to a human agent. That is the fastest route for anything touching a real payment.
What to include
| Field | Why it matters |
|---|---|
| Error ID | Maps directly to the structured server log for that failure. |
| Transaction reference | Lets support trace the money through the provider. |
| Endpoint and timestamp (with timezone) | Narrows the log window. |
| Request payload with secrets removed | Reproduces the validation path. |
| What you expected vs what happened | Separates a bug from a misunderstanding. |
Never paste secrets into a ticket
Do not send passwords, access tokens, provider keys, BVNs or NINs. Redact them before attaching logs. Anything you do send should be treated as compromised and rotated.
Responsible disclosure
- Report suspected vulnerabilities privately through support — never in a public channel.
- Include reproduction steps and impact; do not exfiltrate or modify other users' data while testing.
- Do not run automated scanners or load tests against production.
Before you write in
- Check the error reference — most failures document their own fix.
- Check the changelog for a recent change to the endpoint.
- Confirm the capability actually exists — features marked "not implemented" will not be enabled on request.