Pool Deposit Events

Afriex delivers a real-time notification to your configured webhook URL when a pool account deposit you submitted is rejected during review. Submitting proof of a pool-account payment through Submit Pool Account Payment Proof creates a transaction in IN_REVIEW. An operator then confirms or rejects the bank inflow. Approval surfaces as a TRANSACTION.CREATED event; rejection surfaces here.

Security

See Webhooks Introduction for setup, signature validation, and retry behavior.

Event Types

POOL_DEPOSIT_REQUEST.REJECTED - A submitted pool account deposit was rejected during review

Sample Payload

Pool Deposit Rejected

{
  "event": "POOL_DEPOSIT_REQUEST.REJECTED",
  "data": {
    "transactionId": "69528240ba52c13b669fb239",
    "reference": "pool-account-reference",
    "amount": 5000,
    "currency": "NGN",
    "rejectionReason": "Sender name does not match the submitted proof",
    "resubmissionRequired": true
  }
}

rejectionReason is free text entered by the reviewer. Show it to your operator; do not branch on its contents. Branch on resubmissionRequired instead: true means you can correct the submission and send fresh proof, false means the rejection is final.

This event is delivered by the pool-account review flow only. It cannot be fired from the sandbox Trigger Test Webhook endpoint, so test it by submitting proof in sandbox and having it rejected.

This payload is a flat, purpose-built shape rather than the full transaction object used by Transaction Events. If you need the full transaction, fetch it with Get Transaction using transactionId.

Response

Return 200 (or another 2xx) after successful validation and processing.

Overview

Core Concepts

Balance

Checkout Sessions

Rates

Customers

Payment Methods

Transactions

Webhooks

Media

SME Registration

Security

Event Types

Sample Payload

Pool Deposit Rejected

Response

​Security

​Event Types

​Sample Payload

​Pool Deposit Rejected

​Response

Security

Event Types

Sample Payload

Pool Deposit Rejected

Response