Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pandabase.io/llms.txt

Use this file to discover all available pages before exploring further.

You can request deletion of any store on your account. Deletion is permanent — once we process it, the store stops accepting payments, all access is revoked, and customer-facing pages return 404. Deletion isn’t immediate. We need to verify ownership, settle any outstanding balance, and confirm there are no open disputes before closing the store.

Before you delete

  • Available balance must reach your bank account first. Request a final payout and wait for it to settle.
  • Open disputes must be resolved. If you have disputes in review, you can either let them play out or accept them — but the store can’t be deleted while any are pending.
  • Active subscriptions are cancelled as part of deletion. Customers on recurring billing are emailed and not charged again.
  • API tokens, webhooks, paylinks, storefront stop working the moment deletion is processed.

How to request

Email compliance@pandabase.io with the subject “Delete store — [store ID]”. Confirm:
  • The store ID
  • That you’ve withdrawn your available balance (or want any residual paid out before closure)
  • That you understand deletion is permanent
We may ask follow-up questions through the support thread. Once we confirm there are no blockers, deletion is processed within 5 business days.

What gets deleted

Immediately on processing:
  • The store’s storefront, checkout pages, and paylinks return 404
  • API tokens are revoked
  • Webhook endpoints stop receiving deliveries
  • Active subscriptions are cancelled
  • The store is removed from your dashboard

What we retain

Pandabase is a US-based business. We retain some data after deletion to comply with US federal and state regulations — primarily the Bank Secrecy Act (AML record-keeping), IRS tax requirements, and card-network rules. Retained data is moved to restricted access — encrypted at rest in our compliance vault, accessible only to compliance staff for audits, tax reporting, and law-enforcement requests. It is not used for any other purpose.
CategoryRetained for
Transaction records (payments, refunds, disputes)7 years (IRS / 1099-K reporting)
KYC / KYB documents5 years post-closure (Bank Secrecy Act)
Merchant of record invoices and receipts7 years (US tax recordkeeping)
Bank account details5 years (Bank Secrecy Act)
Suspicious activity reports (if any were filed)5 years from filing date (FinCEN)
Dispute and fraud evidenceUp to 24 months (Visa / Mastercard requirements)
Webhook / API audit logsUp to 1 year
Marketing data, support tickets, profile metadataDeleted on closure

Your rights during the retention period

We process customer and merchant personal data worldwide and respect data-subject rights wherever you’re located — GDPR in the EU, UK GDPR in the United Kingdom, LGPD in Brazil, and equivalent regimes elsewhere. The right to erasure (e.g., GDPR Article 17, Art. 17(3)(b)) doesn’t override US AML and tax obligations — those legal duties take precedence — but the rest of your rights still apply during retention:
  • Right of access — request a copy of what we retain about you.
  • Right to rectification — correct inaccurate information.
  • Right to restriction — ask us to limit processing further (we already minimize during retention, but you can formalize this).
  • Right to object to processing outside the legal-obligation basis.
Email compliance@pandabase.io for any of the above.

Customers

Customers who bought from your store keep access to:
  • Their receipts and invoices through the customer portal
  • Their refund and dispute history
  • Their support cases (read-only once the store is gone)
They can still raise refund or dispute requests directly with Pandabase as the merchant of record. We handle these on your behalf using the retained transaction records.

After deletion

The store ID is permanently retired — it can’t be reused or restored. If you want to open a new store later, you’ll create it as a new entity with a new ID. There is no migration path from a deleted store to a new one.