Notifications / Callback

Once a transaction is finalized, Peex sends a response to the callback URL you have previously configured. This callback mechanism enables real-time tracking of transaction status and two-way communication between your application and the Peex payment service.

Note: Callbacks are configured per service. You must provide a dedicated callback URL for each service you use (remittance, collecte, disbursement). This allows each service to send its notifications to the appropriate endpoint on your side.

Callback URL

Each service has its own callback URL, configured independently:

• Remittance: {{remittance_callback_url}} (provided by you)
• Collecte: {{collecte_callback_url}} (provided by you)
• Disbursement: {{disbursement_callback_url}} (provided by you)
• Method: POST

Callback Security

Peex secures callback requests using Basic Authentication.

• Username: peex (provided by you)
• Password: peex_callback (provided by you)

In production, your credentials will be sent by email. For now, use the above credentials to authenticate Peex HTTP callbacks.

Callback Body

The callback request body is an array containing the payment details of all non-transmitted transactions.

  [
    {
      id: 92,
      amount: 1,
      status: 'paid',
      currency: 'XAF',
      created_at: 2026-04-21T16:29:12.748Z,
      updated_at: 2026-04-21T16:29:25.000Z,
      transaction_type: 'mobile',
      paid_time: 2026-04-21T16:29:21.267Z,
      identifier_by: '677777777',
      track_id: 'callback-TEST002',
      method: 'orange-api',
      payToken: 'CI2604216CF1FBEB847A9AF6DFE0',
      payment_proof: 'CI260421.1729.C07945',
      message: 'transaction paid',
      country: 'CM',
      fund_origin: 'Salary',
      purpose: 'Family maintenance',
      ... // other fields as per your API
    }
  ]