Privacy Policy

Paytena is a payment orchestration and provider-connectivity platform used by merchants and by payment service providers (PSPs). Which hat we wear depends on the data:

• We are the controller for account data, sign-in records, security logs and sales enquiries - the data we need to run the platform itself.
• We are a processor for the data you put into your workspace: payment metadata, business records, and uploaded documents. We process it on your instructions to provide the Service.
• PSPs are separate controllers for anything you submit to them through the platform. Once an application or a document is shared with a PSP, that PSP handles it under its own privacy policy and its own regulatory duties.

• Account and access data - your email address, your name if you give one, which workspaces you belong to and your role in each, the time you last signed in, and session records. Sign-in is by magic link; session tokens are stored hashed, never in the clear.
• Sales enquiries - name, email, company and message when you use the contact form on our home page.
• Business records - legal entity name, registered country and address, company registration number, VAT id, website, business vertical, regulator, licence status and number, and your expected transaction profile (volumes, average value, payment methods).
• Onboarding documents - PDF, PNG or JPEG files up to 10 MB that you upload to your document vault: certificates of incorporation, articles of association, UBO declarations, director identification, proof of address, licences, bank letters, processing statements and similar. These often contain personal data about directors and beneficial owners who are not users of the Service. You upload them and remain responsible for having a lawful basis to do so.
• Payment metadata - amount, currency, country, payment method, your own reference, the provider chosen, the routing decision and why it was made, attempt outcomes, decline category and the raw provider code, fees, and refund and dispute totals.
• Provider credentials and webhook secrets - the API keys you enter for your own payment providers and the signing secrets for your webhook endpoints. These are encrypted with AES-256-GCM before they are written to the database and are never displayed again after creation.
• Security and audit data - an audit trail of significant actions recording the acting user’s email, the action, its target, and the IP address it came from; rate-limiting counters keyed by IP address; and delivery logs for outbound webhooks.

No Paytena screen, API or SDK collects a card number. There are no card fields anywhere in the product. The hosted payment page we redirect to in build mode is a clearly labelled sandbox with outcome buttons, deliberately with no card inputs at all.

The redirect flow exists precisely so that card entry happens on your payment provider’s own hosted page, under that provider’s PCI DSS scope. As a result Paytena does not store, process or transmit primary account numbers, expiry dates, security codes or magnetic-stripe data, and holds no such data to lose.

We use data to operate and secure the Service: authenticating you, routing payment traffic across your own providers, producing your analytics and reconciliation views, transmitting the applications and documents you send to PSPs, maintaining an audit trail, billing you, and preventing abuse.

Aggregated provider performance signals (approval rates, fees, latency) train the routing engine. That model works on payment and provider attributes, never on identified individuals.

We do not sell data and we do not use it for advertising.

The routing engine automatically chooses which of your providers should attempt a payment, and may retry a decline on a backup provider. That is a decision about a transaction and a provider, not a profile of a person.

Decisions on PSP applications - approval, rejection, requests for more information, pricing - are made by the PSP’s own staff in their portal. Paytena does not underwrite applicants and does not decide them automatically.

• PSPs you apply to - the answers on your application form, and only the documents you explicitly attach to that application. Each share is per document and per application, and you can revoke it from your document vault. Nothing is shared with a PSP you have not applied to.
• Your own payment providers - the transaction details needed to authorise a payment, sent using the credentials you configured, under your own agreement with that provider.

We rely on the following sub-processors to run the Service:

Some of these providers operate infrastructure outside your country, including in the United States, and we rely on the transfer safeguards they offer in their data-processing terms. We will also disclose data where we are legally required to.

We set two cookies, both strictly necessary. There are no analytics, advertising or third-party tracking cookies, which is why you are not asked for cookie consent.

A daily job enforces these windows automatically. Anything not listed is kept for the life of the workspace.

Deleting a workspace deletes its data - members, payments, providers, business records, documents and audit entries - permanently and by cascade. Export anything you need first.

• Provider credentials, webhook signing secrets and every uploaded file are encrypted with AES-256-GCM by the application before they reach any storage backend, so the storage backend never holds plaintext.
• Documents are only ever served through routes that check your authorisation first; the underlying storage URL is unguessable and yields ciphertext even if it leaks.
• Session tokens and API keys are stored as hashes. API keys are shown once, at creation.
• Workspace isolation is enforced in the data layer, not only in the interface, and sensitive actions are written to an audit trail.
• Because we hold no cardholder data, the most sensitive category in payments is simply out of scope here.

Subject to applicable law you may ask us to access, correct, export or delete your personal data, or object to a particular use. Workspace owners can export payment data and delete the workspace directly from the dashboard at any time.

Where we hold data on behalf of a merchant or a PSP - for example, personal data inside an uploaded document - we will pass your request to that organisation, which is the controller for it, rather than acting on it ourselves.

You also have the right to complain to your local data protection authority.

If we change how we handle data we will update this page and its date, and tell workspace owners about material changes.

For privacy requests or questions, use the contact form on our home page.