PaymentIQ dashboards: understand your payment figures.

What should your dashboard tell you?

Start with a question your team needs to answer. For example: “Why did card deposits fall yesterday?” A useful dashboard lets you see whether fewer customers tried to pay or more attempts failed.

• How many deposits and withdrawals were attempted, completed or left pending?
• Which countries, payment methods or providers had more failures?
• What changed compared with the previous period?

What might that look like?

The chart below compares two providers over time using invented figures. It is a design example, not a live PaymentIQ screen or a client result. If one line drops, the next step is to check the transactions behind it.

Seeing more failed payments? Read how to investigate them.

What does a success rate actually mean?

If 820 of 1,000 payment attempts succeed, the success rate is 82%. But 1,000 attempts does not mean 1,000 customers: one person may have tried several times.

• Decide whether you are measuring payment attempts or individual customers.
• Use the same dates, time zone and treatment of pending payments when comparing reports.
• Show transaction counts beside percentages. A high rate based on ten payments says much less than one based on thousands.

Why do two reports show different numbers?

One report might include pending payments while another only counts completed ones. Filters, time zones, duplicate records or export limits can also explain a difference. I check these before treating a change in a chart as a business result.

• Take the same time period and compare the transaction counts and amounts.
• Check which records each report includes or leaves out.
• After changing a query or dashboard, check the totals again.

Can you build dashboards outside PaymentIQ?

Yes. Depending on the data and access available, I can build reports in PaymentIQ or combine its data with provider and platform records in an external dashboard.

• Bring the figures your operations and finance teams need into one view.
• Agree how often the report needs updating.
• Make it clear where each number comes from and how it is calculated.

What is reconciliation, and what did I build?

Reconciliation means comparing records from different systems to check that they agree. For example, a payment may appear in a provider's report but be missing from your platform report. The tool flags the difference so your team can investigate.

• I designed, built and tested a reconciliation application on my own, without a developer or delivery team.
• It imports PaymentIQ and provider data, matches transactions, highlights differences and keeps a record of review decisions.
• The tested application and technical documentation were prepared for engineering handover.
• For a custom tool, we first agree which records to compare. Matching individual transactions is different from checking bank settlements or accounting balances.

How does this help day-to-day operations?

A dashboard can show the cases that need attention, such as a withdrawal waiting for review or a transaction that does not match a provider report.

• Separate withdrawals approved for payment from withdrawals actually paid.
• Show who needs to investigate each unresolved case.
• After a rule change, compare results and volumes to see what changed.