Skip to main content

Reporting

Clients rely on reports to reconcile transactions, track performance, and meet compliance requirements.
Nopan provides flexible options for retrieving reports depending on your operational needs:

  • Secure file transfer (SFTP)
  • Manual download through the merchant portal
  • Programmatic access through REST APIs
info

PGP encryption is supported for clients that require end-to-end confidentiality. This can be enabled on request and applied consistently across all delivery channels.

Available Report Types​

Merchant report categories

Report Type
Description
Frequency
Settlement Report
Details of funds settled to your bank account including fees and adjustments.
Daily
Transaction Report
Line-item breakdown of processed transactions (approved, declined, refunded, reversed).
Daily or On-Demand
Reconciliation Report
Cross-reference between payment events and bank settlements for audit and accounting.
Daily
Dispute Report
Overview of chargebacks, disputes, and their current resolution status.
Daily or Weekly
Activity Summary
High-level summary of volumes, values, and operational KPIs.
Daily or Monthly
info

Additional report types can be provisioned depending on your integration and market requirements.
Reach out to your Nopan technical contact for custom formats.

Delivery Options​

1. SFTP Delivery​

Reports can be automatically deposited on a secure SFTP server. You can choose:

  • Use Nopan-hosted SFTP - we provision accounts for your team.
  • Use your own SFTP - Nopan pushes reports directly to your infrastructure.
tip

PGP encryption can be enabled so that each file is encrypted with your public key before delivery.

2. Merchant Portal​

You can log into the Nopan Merchant Portal and manually download available reports.
This is useful for finance teams or ad-hoc reporting needs.

3. REST API Access​

Reports can also be retrieved programmatically through the Reports API, enabling full automation:

GET /reports/{reportType}?date=2025-08-01
Authorization: Bearer <access-token>
tip

The API supports filtering by date ranges, report type, and format (CSV, JSON).

info

Authentication is handled the same way as other Nopan APIs: with mTLS and access tokens.

Optional : PGP Encryption​

Nopan supports optional PGP encryption for clients requiring data-at-rest confidentiality outside TLS.

  • Your public key must be registered with Nopan in advance.
  • Encrypted reports will carry the .pgp file extension.
  • Reports can still be delivered unencrypted if your systems operate inside a controlled environment.

Example decryption:

gpg --output settlement.csv --decrypt settlement.csv.pgp

Error Handling​

When retrieving reports, you may encounter errors:

Scenario
HTTP Status / Error
Recommended Action
Report not found (wrong date or type)
404 Not Found
Verify that the report type/date combination exists.
Unauthorized API request
401 Unauthorized
Ensure a valid OAuth token is provided.
SFTP connection refused
—
Check credentials and network access.
Decryption failure
—
Confirm that your PGP key matches the one registered with Nopan.
warning

Never process financial data or trigger business logic on unverified or corrupted reports.