LLedgerline DocsAPI v2.4Want docs like this? Talk to Doc Foundry

Compliance / Data handling

Data handling

What Ledgerline stores, how it is protected, how long it is kept and which responsibilities stay with you. Share this page with your compliance team before you go live.

Who is responsible for what

AreaLedgerlineYou
Card dataCollects and stores card numbers on hosted checkout. Card numbers never reach your servers.Use hosted checkout or the Ledgerline SDK. Never collect card numbers in your own forms.
API keysEncrypts keys at rest and lets you roll them at any time.Keep secret keys on your server and limit who can see them.
Customer dataProcesses it to complete payments, as your data processor.Tell customers you use Ledgerline, in your own privacy notice.
WebhooksSigns every event.Verify signatures and serve your endpoint over HTTPS.

What we store

DataWhyKept for
Payment records: amount, status, reference, timestampsSettlement, reporting and disputes7 years after the payment
Customer email and nameReceipts and dispute handling7 years after the last payment
Card details (tokenised)Completing and refunding card paymentsUntil the card expires or you delete the customer
API request logsSupport and security investigations90 days

Your own record-keeping obligations may differ from ours. Check with your compliance team which retention periods apply to your records.

How data is protected

Customer data requests

If a customer asks you to delete or export their data, send the request through Dashboard → Customers → Data requests. We complete it within 30 days, except for records we must keep by law, which we explain in our response.

Need evidence for an audit or a security review?

Account owners can download our current security overview and data processing agreement from Dashboard → Settings → Compliance.

Last updated 28 October 2026