Customer work, connected.

Help & supportMyAccount
Pixie CRM
Try Pixie for a 14-day free trial
Audit, security and tenant isolation · How-to guide

Disconnect Tide tokens without deleting historical reconciliation evidence

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Detailed client guidance covering disconnect Tide tokens without deleting historical reconciliation evidence, with exact eligibility, security, verification and troubleshooting boundaries for the shipped Tide payment and Open Banking controls.

Audience: Administrators and authorised payment operations staffPermission: AuditModule v1.0.0
Jump to steps
Where to goTide Payments → Audit
Before you startConfirm the intended tenant, remote account or invoice context, and your Audit access. Keep credentials and tokens out of screenshots, tickets and exported evidence. If a previous write may have reached an external service, verify remote state before retrying.

What this guide helps you do

Detailed client guidance covering disconnect Tide tokens without deleting historical reconciliation evidence, with exact eligibility, security, verification and troubleshooting boundaries for the shipped Tide payment and Open Banking controls. This article is intentionally scoped to the behaviour enforced or exposed by the supplied module and does not treat provider marketing features as implemented integration capabilities.

How it works

Tide payment instructions, AIS transaction import, exact reconciliation, native invoice payment status and audit evidence are connected but separately verifiable stages. A payment instruction is not proof of receipt; a bank transaction is not a certified invoice payment until it passes the reconciliation gates.

Follow these steps

  1. Open Tide Payments → Audit.
  2. Confirm the intended tenant, invoice/connection/transaction where applicable, and your Audit access before continuing.
  3. Open the relevant connection/payment/reconciliation event in the audit log.
  4. Capture event, actor, entity, request identifier and timestamp.
  5. Verify connection/transaction evidence without exposing tokens or private keys.
  6. Preserve the audit trail before changing credentials during an incident.

Settings to check

This guide’s focusDetailed client guidance covering disconnect Tide tokens without deleting historical reconciliation evidence, with exact eligibility, security, verification and troubleshooting boundaries for the shipped Tide payment and Open Banking controls.
AuditSettings, connection and reconciliation actions write module audit records with event/entity/actor/request context where available.
Token secrecyOpen Banking tokens are encrypted at rest and never intentionally echoed back to the settings form.
TransportAPI calls enforce TLS verification and safe origin/path controls and generate an x-fapi-interaction-id UUID for request tracing.
Tenant isolationConnection, payment, transaction and reconciliation records are stored within the tenant application data scope.
Evidence preservationDisconnecting or deactivating does not remove historical reconciliation and audit evidence.

Check it worked

Reopen the intended invoice, Tide transaction/reconciliation register and audit evidence. Confirm the full Tide transaction identifier where available, exact amount/currency/reference, reconciliation state, native invoice payment and latest timestamps. If the bank-feed state cannot be independently verified, keep the task unresolved and use the supported troubleshooting flow.

Frequently asked questions

When is an invoice actually treated as paid?Only when an eligible Tide credit is exactly reconciled and the native gateway payment is recorded; showing transfer instructions is not payment confirmation.
Can staff override a close-but-not-exact bank match?The automatic flow intentionally requires exact eligibility, reference and current outstanding amount. Investigate the bank/reference/invoice state instead of weakening the control.
What should I include in a support case?Include invoice ID, Tide transaction ID if available, reference, amount/currency, booking timestamp, connection status and visible error. Never include access/refresh tokens or private keys.
Does disconnecting remove history?No. Active connection tokens/state can be removed while historical payment, reconciliation and audit evidence is retained.

Technical basis for this guidance

This guide was checked against the supplied module code paths: tide_payments.php; controllers/Tide_payments.php; controllers/Tide_payments_client.php; models/Tide_payments_model.php; helpers/tide_payments_helper.php; libraries/Tide_gateway.php; libraries/Tide_open_banking_client.php; libraries/Tide_partner_client.php; views/admin; views/client/pay.php; install.php; config/routes.php. It documents shipped behaviour, validation, routes and evidence controls; it does not claim successful live provider network calls from offline inspection.

Common mistakes to avoid

  • Work in the intended tenant and remote accounting/business context.
  • Do not paste credentials, access tokens, refresh tokens or private keys into tickets or notes.
  • Do not bypass a missing mapping, validation error, permission gate, duplicate check or remote-verification requirement.
  • Do not repeat a non-idempotent write until you know whether the previous request reached the remote service.
  • Keep native record, remote evidence and audit/history state aligned before closing the task.
Provider and accounting boundaryDisconnecting or deactivating does not remove historical reconciliation and audit evidence.
Browse connected topics: Audit, security and tenant isolation Tide Payments Accounting & Bookkeeping
Review Tide security evidence after a reconciliation incidentUnderstand which Tide capabilities are available in this releaseAccounting & Bookkeeping guides

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page