Prepared for paysafecard, Vienna

Paysafe is investing in innovation and marketing while paying down debt. The Salesforce platform behind paysafecard’s partner pipeline has to be resilient under DORA.

paysafecard runs B2B lead nurturing for Europe and the US in Salesforce Pardot, and Paysafe recruits Salesforce technical architects. DORA has applied to e-money institutions since January 2025.

Book the session Why Flosum, specifically

$447.4mPaysafe revenue Q2 2026, up 4%

$206.6mDigital Wallets revenue Q2 2026

20%mid-term Product Vitality Index target

$2.5bntotal debt, 30 June 2026

Where paysafecard is headed

Paysafe is pairing product innovation with tighter financial discipline.

Revenue grew 4% in Q2 and 7% in the first half, with PaysafeWallet driving user growth in Europe.

Paysafe refinanced most of its capital structure in August 2026 and is focused on execution and debt reduction.

Investment in innovation, marketing and data commercialisation continues.

Innovation

Product Vitality Index toward 20%

Marketing

Investment up $7.1m in Q2

Discipline

Debt reduction priority

Pressures

Regulation and capital discipline leave no room for avoidable platform incidents.

DORA

ICT risk, testing and backup obligations for e-money institutions.

Debt

Net debt $2.3bn.

Partner growth

B2B leads for Europe and the US.

Personal data

Partner and consumer data under GDPR.

What leadership has said

Paysafe’s CEO ties returns to investment and execution.

Our investments in innovation, marketing, and data commercialization are continuing to generate returns, with our Product Vitality Index remaining on track toward our mid-term target of 20%.
Bruce Lowthers, CEO, Paysafe
Innovation at pace needs releases that do not break.

As we enter the second half of the year, we remain focused on execution, deleveraging, and building on the durable growth opportunities across our global network of consumers and merchants.
Bruce Lowthers, CEO, Paysafe

paysafecard’s Salesforce reality

paysafecard’s partner marketing and Paysafe’s CRM architecture run on Salesforce.

What is published.

Pardot: B2B lead nurturing and grading at paysafecard
Salesforce architecture: Paysafe recruits a Salesforce Technical Architect
CRM team: Plans implemented into Pardot with the CRM team
Scope: Full cloud list not published

What’s at risk

Under DORA, an untested change or unrecoverable record is a compliance finding, not just an outage.

If this happens	Why it is plausible	What it costs
Faulty release to lead scoring	Pardot lead grading	Partner pipeline stalls.
Records lost	Partner and lead data	No proven recovery.
Backup in same environment	DORA Art. 12 segregation	Supervisory finding.
Real data in test	Partner contacts	GDPR exposure.

Why it’s imperative for paysafecard to choose Flosum

Why it’s imperative for paysafecard to choose Flosum: DORA asks for proof of control, and Flosum produces it.

Each row ties a paysafecard priority to a control.

paysafecard initiative	Exposure today	Flosum capability	Outcome
DORA	Uncontrolled ICT change	Audit trail and approvals	Change records on demand
DORA backup	Backup tied to production	Segregated backup in your own cloud	Art. 12(3) aligned
Marketing pace	Release breaks campaigns	Automated deployments with rollback	Campaigns stay live
GDPR	Real data in test	Masking at sandbox creation	No real partners in test

Flosum is rated 4.80 on G2 and 4.97 on AppExchange.

Flosum DevOps

One governed pipeline for Salesforce and Pardot changes.

Marketing changes move fast.

Where it bites today

CRM and Pardot work together

What Flosum changes

Admin clicks, developer code and AI-generated changes all go through the same version control, approvals and audit trail.
Metadata is merged component by component, so two people editing the same Flow or profile do not overwrite each other.
A dependency graph catches the deployment that would fail before it reaches production.
If a release goes wrong, one-click rollback puts the org back.
Release evidence is produced as the work happens and kept beyond Salesforce’s native 180-day Setup Audit Trail.
Teams on Flosum report 40% higher development velocity and 75% fewer merge conflicts.

How paysafecard would measure it

Lead time from request to production
Failed or rolled-back deployments per quarter
Changes shipped with a complete approval record

Flosum Backup & Archive

Segregated backup gives paysafecard the recovery proof DORA expects.

Recovery must be proven.

Where it bites today

DORA
Salesforce’s Weekly Export runs every 7 days and deletes files after 48 hours; its Data Recovery Service costs $10,000, takes 6 to 8 weeks and returns no metadata.

What Flosum changes

Backups run near-continuously, and restores can target a single field, a record or the full org at a point in time.
Data, metadata, files and the relationships between records are all protected.
Backups can live with Flosum or in your own AWS, GCP, Azure or private cloud, with keys you hold.
Backups sit completely apart from Salesforce, the segregation DORA Article 12(3) asks for.
Salesforce bought Own in 2024. Flosum stays independent of the platform it protects.

How paysafecard would measure it

Recovery point objective for the org
Time to restore a single corrupted record set
Restore drills passed per year

Flosum Sandbox Management

Warm-start sandboxes let architects test on realistic data.

Architecture work needs realistic orgs.

Where it bites today

Salesforce Technical Architect role
Full sandboxes refresh on a 29-day clock

What Flosum changes

Developer sandboxes arrive ready to work: Flows disabled, PII masked, production data seeded, access locked and the pipeline reconnected.
Full-copy sandboxes stay in continuous sync with production, so the 29-day refresh window stops setting the schedule.
Teams need fewer full-copy licenses, and the 25 to 100 developer sandboxes in Enterprise editions stop sitting idle.

How paysafecard would measure it

Hours from refresh to a usable sandbox
Full-copy sandbox licences in use

Sandbox Management is in early access; Flosum offers a 30-minute working demo on your own metadata.

Flosum Data Masking

Masking removes partner and consumer data from test orgs.

A payments brand cannot leak data.

Where it bites today

GDPR

What Flosum changes

Masking happens before data lands in the sandbox, which turns it from a best-effort cleanup into a guarantee.
Because masking is part of sandbox provisioning, every new developer sandbox is masked by default.
Encryption keys can stay with your team.
Masked sandboxes are locked to a minimal set of users, which supports GDPR, HIPAA and GxP programs.

How paysafecard would measure it

Share of sandboxes masked at creation
Real customer records found outside production (target: zero)

Org protection from configuration errors

Drift detection catches direct changes to production.

DORA expects controlled change.

Where it bites today

DORA

What Flosum changes

Automatic org synchronization flags drift when someone changes production outside the pipeline.
Release evidence is produced as the work happens and kept beyond Salesforce’s native 180-day Setup Audit Trail.
If a release goes wrong, one-click rollback puts the org back.

How paysafecard would measure it

Out-of-process changes detected per month
Time to detect and revert a bad change

Why now

DORA supervision is live and Paysafe’s second half is focused on execution.

Both point to closing control gaps now.

Jan 2025DORA applies

Aug 2026Refinancing completed

H2 2026Focus on execution and debt reduction

Mid-termProduct Vitality Index 20%

The first 90 days

Map Salesforce and Pardot release flow
One change through a Flosum pipeline
Segregated backup and restore drill
DORA control report

Next step

A 45-minute session with the CRM team: one release, one restore, one DORA report.

Bring the CRM owner and the ICT risk lead.

Your org in a Flosum pipeline
Timed restore of lead records
DORA Art. 12 backup mapping

Book the session

Prepared by Flosum for paysafecard, October 24, 2026. paysafecard names and program names belong to their owners.