Transactions

Every payment attempt is a transaction. The Transactions page lists them for the current Brand and lets you confirm, correct and refund them.

Transactions are created by the Payment API, invoices and payment links. You can't create one by hand here.

Statuses

Status	Meaning
Pending	The customer says they've paid, and Paybob is waiting to confirm it: for example, a wallet payment waiting for its SMS.
Completed	The payment is confirmed.
Partially refunded	Part of a completed payment was refunded.
Refunded	The whole payment was refunded.
Failed	The payment didn't go through.
Canceled	The payment was canceled.
Voided	The payment was voided.

A checkout the customer opened but never paid stays in an internal "started" state and isn't listed here.

The transaction list

Tabs along the top filter by status, each with a count: All, then one tab per status.

The table shows the Customer, Gateway, Amount, Net Amount, the gateway's Transaction Id, the Date and the Status. Filter by Gateway, Currency or Date Range, and search by Paybob's payment ID, the gateway's transaction ID, or the customer's details.

How amounts are calculated

Figure	Formula
Total Amount	Amount − discount + processing fee: what the customer actually pays.
Net Amount	Total amount − everything refunded so far.
Maximum refundable	The net amount.

Approving a payment

If you've confirmed a Pending payment yourself, for example by checking your bank app, click Approve in the row's menu. The transaction becomes Completed, and a webhook is sent to the customer's website or app straight away.

To approve several at once, select them and use Bulk Actions → Approve. Their webhooks are sent within about a minute. Transactions that aren't Pending are skipped.

Most wallet payments don't need approving by hand: Paybob completes them automatically when the payment SMS arrives. See SMS verification.

The transaction page

Click View to open a transaction. It shows the payment status and Paybob's Payment ID, then tabs:

Transaction Details: amounts, currency, gateway and either the gateway's Transaction ID or a View Slip button when the customer uploaded a payment slip instead.
Customer: the name, email and phone captured with this payment. These are kept exactly as they were at the time, even if the customer's record changes later.
Refunds: the refunded total and the latest reason. Shown once something has been refunded.
Metadata: extra data your website or app sent with the payment. Shown when there is any.
More Info: extra details collected at checkout, such as answers to a payment link's custom fields and uploaded files. Shown when there are any.

Actions

Action	What it does
Edit	Set the status or the gateway's transaction ID by hand, to correct a mistake.
Send IPN	Send the payment's webhook again, without changing anything. Shown when the payment has a webhook address.
Refund	Refund part or all of a completed payment.
Delete	Delete the transaction permanently.

Refunding

Click Refund, enter the Amount (leave it empty to refund everything that's left) and a Refund Reason, and confirm. The amount can't be more than the maximum refundable, which is shown under the field. A refund of everything that's left makes the transaction Refunded; anything less makes it Partially refunded. You can refund a partially refunded payment again.

Refunding here doesn't send money back

Refund records the refund in Paybob and tells your systems about it. Return the money to the customer through your payment provider or bank yourself.

Paybob keeps the total refunded and the most recent reason, not a separate record for each refund.

Editing by hand

Edit changes the status without the usual checks, for example to move a payment to Canceled or Voided, or to fix a status set by mistake. It doesn't recalculate refunds. Setting a transaction to Completed also marks its invoice as paid, if it came from one. Use Refund for refunds, not Edit.