§Compliance
Designed for European rules, and clear about who is responsible for what.
VEYRA is a technology platform. Regulated activities — holding funds, executing payments, customer due diligence — will be carried out by authorised partners. Our job is to design the software so that those obligations are easy to meet and impossible to bypass.
Everything on this page describes design considerations. VEYRA does not hold licences or certifications and does not claim any.
01Frameworks we design for
What each rule asks, and how the product answers.
| Framework | What it is about | How VEYRA is designed for it |
|---|---|---|
| PSD2 and SCA | Strong Customer Authentication for electronic payments in the EEA | 3-D Secure requested through providers when required; exemptions only where the provider supports them; outcome stored on each payment |
| PCI DSS | Security of cardholder data | Scope minimisation: card data entered only in provider-hosted fields, tokens only on our side |
| GDPR | Protection of personal data | Data minimisation, EU hosting by design, access controls, retention rules and data-subject request workflows |
| AML/CFT | Anti-money-laundering and counter-terrorist financing | Customer due diligence performed by authorised partners; VEYRA collects information through hosted flows and pauses payouts until checks pass |
| DORA | Digital operational resilience in finance | Incident logging, dependency mapping, provider health monitoring and tested fallbacks, designed to support partners’ obligations |
| EU sanctions | Restrictive measures adopted by the EU | Screening of businesses and payouts by partners; VEYRA blocks flows flagged by screening |
02Who does what
A clear division of responsibilities.
VEYRA
- Software for payments, checkout, payouts and reconciliation
- Double-entry ledger and audit trail
- Routing decisions and their explanations
- Security of the platform and of merchant data
Authorised partners
- Holding and moving client funds
- Executing card and bank payments
- Customer due diligence and sanctions screening
03Capability status
What works today, and what is waiting for what.
Every capability has two statuses: in the sandbox, and in live mode. We update this table as things change.
| Capability | Sandbox | Live |
|---|---|---|
| Payment Intents and card payments | Working in sandbox | Awaiting provider credentials |
| 3-D Secure / Strong Customer Authentication | Working in sandbox | Awaiting provider credentials |
| Hosted Checkout and Payment Links | Working in sandbox | Awaiting production readiness review |
| Webhooks with signatures and replay | Working in sandbox | Awaiting production readiness review |
| Bank account verification (IBAN, name check) | Working in sandbox | Awaiting provider credentials |
| Payouts to bank accounts | Working in sandbox | Awaiting provider credentials |
| Subscriptions and invoices | Working in sandbox | Awaiting production readiness review |
| Marketplaces (Connect) and seller onboarding | Working in sandbox | Awaiting compliance approval |
| Smart Routing across providers | Working in sandbox | Awaiting provider credentials |
| Live processing as a whole | Working in sandbox | Awaiting production readiness review |
?FAQ
Questions, answered
Is VEYRA a licensed payment or e-money institution?
No. VEYRA does not hold a payment institution or electronic money licence. Live payments will be operated by partners who are authorised to provide them.
Who will be my contractual counterparty for payments?
This will be set out in the live terms once partner agreements are final. We will make it explicit before you accept any live terms.
Why does a page about compliance contain no certificates?
Because we have not earned them yet, and showing logos we do not hold would be the opposite of compliance.
Need details for your own compliance review?
We will share our design documents and regulatory assumptions on request.