Payments built for the way
your business really runs.

Voice Payment, Premium SMS (PSMS) and Direct Carrier Billing (DCB) let a customer pay through their mobile account instead of a card or bank transfer. This method set fits situations where the customer relationship is mobile-first and a card or bank login is friction, not a convenience.

Mandate issuance, return-code handling and scheme-timed pre-notification are built into the flow rather than left to manual tracking. Where mandate handling stays outside the integrated flow, reconciliation and audit preparation fall back onto manually cross-checked records, which is the concrete cost a fragmented setup adds later, not just an abstract risk.

The mandate lifecycle

• Mandate issuance: Captured and stored as part of the integrated flow
• Return-code handling: Processed within the same flow, not tracked separately
• Pre-notification: Timed per scheme requirement
• B2B perspective: Applies to B2B SEPA use as well as consumer use

Paysafecard and other prepaid and voucher methods give customers a way to pay without a card or bank account, commonly relevant for digital goods and entertainment purchases where the customer prefers not to enter card details.

Available methods:

• Paysafecard
• Other selected prepaid and voucher-based methods

Configured only where they match:

• Merchant category
• Customer profile
• Market

Availability is use-case specific, evaluated against the merchant setup and confirmed during onboarding, not surfaced by default.

Worth raising early if you’re in digital goods, digital entertainment or content-driven services with established prepaid behaviour.

Relevant when: part of your customer base actively avoids card payments, or your market has established prepaid behaviour that card-only checkout would exclude.

Card-on-file and SEPA Direct Debit are handled as core building blocks under PCI-DSS standards, so stored-credential data stays inside a controlled scope rather than spreading across separate systems. Structured retry logic reduces the specific risk of failed renewals being retried in a way that damages the customer relationship or issuer standing, rather than being retried blindly.

Built for controlled recurring billing

• Card-on-file handling under PCI-DSS standards
• SEPA Direct Debit as a recurring-billing method
• Structured retry logic for failed renewals

Card data & scope

• Card data: managed to PCI-DSS standards, designed to keep it out of the merchant environment.
• Merchant scope: reduced, so there’s less for your team to manage directly.

Handled as part of the setup, not default checkout behaviour:

• Method rules
• Credential handling
• Retry logic

For complex subscription structures, multiple billing cycles or mixed recurring methods, the setup conversation should cover the full credential and method logic before integration begins.

What CFO and Compliance teams should notice: how credentials are handled at the payment layer affects what your team must certify and audit. A provider designed to keep card data out of your environment is worth evaluating carefully against your compliance workload.

Each partner route carries a different commercial structure and a different technical and onboarding path. The comparison below is a starting reference; the exact terms for any route are confirmed directly with DaoPay.

They differ across:

• Commercial structure
• Technical setup
• Merchant onboarding
• Regulatory considerations

DaoPay shapes the contracting and operating structure around the model, starting from how you bring merchants: the referral or processing relationship, the merchant profile and the markets involved.

The Onboarding PreCheck applies to the cases a partner brings forward. Partners who pre-qualify enter with a clearer merchant case and less friction; broad, unqualified portfolios create more complexity for both sides. DaoPay supports partners building a structured, sustainable processing relationship, not just volume.

Automation handles volume. A human provides context where volume alone cannot make the right call. This is not a rejection of technology — automated checks still carry most of the workload — it is a defined point where a person, not a scoring model alone, decides.

DaoPay reviews applications with a human risk analyst, not only an automated score. The analyst weighs the full business case: model, market, category, transaction profile and regulatory context. It takes longer than a form submission, and produces a better-documented, accountable decision.

Risk signals, 3-D Secure strategy and human oversight work together so payment decisions stay accountable at every layer. When disputes reach the scheme, representation support is available within the agreed operating model.

How this connects to onboarding: the Onboarding PreCheck is the first stage: before you commit to integration, DaoPay assesses fit. The risk review is the natural continuation of that qualification, not a separate gate that appears later.

T+1 payout, where the business case supports it, is paired with transaction-level, scheme-fee-level and payout-level reconciliation, so each fee line stays traceable rather than folded into a single settlement figure.

Finance teams rarely get the full cost structure before the first settlement file arrives; blended rates obscure scheme fees, reconciliation files that don’t map to invoice lines create audit overhead, and settlement timing that’s never confirmed operationally creates cash-flow uncertainty at the worst moment.

DaoPay structures the settlement and reconciliation layer before go-live, not after.

Settlement

Timing and funding route are agreed upfront. Where the business case supports it, settlement runs T+1 with direct funding to your nominated account in covered acquiring categories.

Confirmed before go-live, so your finance team operates from a known structure:

• Timing
• Currency baseline
• Funding route

Reconciliation

Available at transaction, scheme-fee and payout level, through the merchant portal, scheduled export or API pull.

Every fee line visible

Shown separately per transaction, where the commercial setup supports it:

• Interchange++
• Scheme fee
• DaoPay margin

Line-by-line visibility for period close, audit preparation and operational cost review.

Blended pricing is available on request, for merchants whose volume and model support it.

What finance teams should ask before go-live: “Can you show me the settlement structure, timing and reconciliation format before we sign?” If a provider can’t answer clearly before onboarding, it won’t improve afterwards.

Additional currencies beyond the default set are confirmed upon request as part of the commercial setup, so currency needs can be planned into the contracting stage rather than discovered after go-live.