Security + Data

How FeeSuite handles payment and bank records.

FeeSuite is built around the payment and bank records required for reconciliation, with controls designed to keep that data connected to the work, accessible to the right people, and protected throughout the workflow.

Use the records required for reconciliation. Keep the scope clear.

FeeSuite works with the payment and banking records needed to reconcile merchant activity, including processor or merchant statements, bank deposits, fees, reserves, chargebacks, adjustments, and related supporting records.

The goal is not to create another copy of the payment environment. FeeSuite brings together the records required to explain the reconciliation and keeps them connected to the resulting review, decisions, and history.

Bank activity enters the reconciliation in context.

FeeSuite supports bank connectivity as part of the reconciliation workflow so deposits can be compared directly with processor and merchant statement activity.

Where supported, bank connections may be provided through third-party connectivity providers such as Plaid. Available connection methods may vary by customer configuration.

Who can see a reconciliation.

FeeSuite is designed to limit access to authorized users and support controlled access across merchant accounts, entities, and reconciliation responsibilities.

Administrative, technical, and organizational safeguards are used to protect the information processed through the platform. Specific controls, infrastructure, encryption, retention, and access-management practices are documented as part of FeeSuite’s security program and customer agreements.

Keep the reconciliation traceable.

The records supporting a reconciliation remain connected to the resulting matches, offsets, exceptions, review activity, and approvals. This gives teams a traceable history without requiring them to reconstruct the work from separate files later.

Data retention, deletion, export, and customer-data requirements may vary based on the applicable service agreement and customer configuration.

Compliance documentation.

FeeSuite maintains security and compliance practices appropriate to the financial workflows it supports. Current attestations, reports, and compliance documentation are made available based on their applicable scope and availability.

Security FAQ
FeeSuite supports bank connectivity within the reconciliation workflow. Connection methods vary by customer configuration and may include supported third-party connectivity providers.
FeeSuite uses the processor, merchant, banking, fee, reserve, chargeback, adjustment, and supporting records required to perform and explain the reconciliation.
Access is limited to authorized users based on the configuration and permissions established for the customer environment.
Retention requirements depend on the applicable service agreement, customer configuration, and legal or operational requirements.
Yes. Additional security, compliance, and data-handling information can be provided during the evaluation and contracting process.
Security questions

Talk through your data requirements with us.

We can walk through how FeeSuite fits into your reconciliation environment and answer questions about connectivity, access, and data handling.

Security + Data
1Connectivity
2Access
3Data handling
Request a Demo