DreamPay

DreamPay provides embedded and private-label payment services for merchant acquirers, financial institutions, insurers, software platforms, and marketplaces. Clients can add digital and mobile inbound and outbound payments within their own software applications, and DreamPay also offers point-of-sale solutions for in-person payments. Online transactions can be one-time or recurring, by credit or debit card or bank transfer through ACH in the US and EFT in Canada. Checkout options include hosted payment pages, embedded checkout, and one-click payments with stored cards. Payout methods include ACH, EFT, real-time payments, virtual cards, Interac e-Transfer, and cheques. A dashboard tracks transaction volume, success rates, revenue, refunds, and chargebacks. APIs support payment data integration for reconciliation and webhook updates on payment outcomes and status changes. Dream says the platform follows PCI DSS and SOC 2 standards, uses end-to-end encryption for payment transactions and payouts, and includes KYC and AML tools; its security page also lists GDPR compliance. A zero-fee option passes processing fees to customers using a flat or percentage-based structure. Revenue-sharing terms can be customized, with earnings dependent on transaction volume. Pricing is available on request.

DreamPay combines embedded payment, payout, point-of-sale, and reporting options for organizations adding payments to their services. Pricing is on request, and its zero-fee model shifts processing fees to customers.

DreamPay is aimed at banks and other financial institutions, insurers, software platforms, marketplaces, and large enterprises seeking embedded payment or payout services. Its point-of-sale offering may also suit in-person merchant payments.

DreamPay is a private-label payments platform for organizations that need acceptance, payouts, and payment operations inside their own products. It is best suited to banks, insurers, software platforms, marketplaces, and large enterprises rather than a small merchant seeking a standalone checkout. Its broad payment rails and integration model are persuasive, but buyers must obtain a custom quote and decide whether passing fees to customers fits their market.

Overview

DreamPay combines online and in-person acceptance with outbound disbursements. Clients can launch digital and mobile payment capabilities within existing software and present them under their own brand. That makes it useful when payments are part of a wider service, especially where a platform must both collect money and send it onward.

Online acceptance covers one-time and recurring credit or debit card payments plus pay-by-bank transactions. ACH is supported in the United States and EFT in Canada. Embedded bank transfers settle to the platform’s bank account in one to two business days through ACH or EFT, a timing window that should be considered when planning cash flow.

Key features

Checkout and acceptance

Hosted payment pages, embedded checkout, and one-click payments with stored card options provide different levels of control over the customer journey. Point-of-sale capabilities extend the product to in-person merchant payments, so an organization can address online and physical transactions within the same broader offering.

Payouts and transfers

Outbound options include ACH, EFT, real-time payments, virtual cards, Interac e-Transfer, and cheques. This is a flexible set of rails for platforms paying suppliers, claims, sellers, or other recipients, although the best option will depend on each recipient’s country and required speed.

APIs, reporting, and controls

APIs support inbound and outbound payment embedding, payment-data integration for reconciliation, and webhooks that report outcomes and status changes. The dashboard tracks transaction volume, success rates, revenue, refunds, and chargebacks, giving operators the measures needed to monitor payment performance and exceptions.

Dream says the platform follows PCI DSS and SOC 2 standards, uses end-to-end encryption for transactions and payouts, and includes KYC and AML tools alongside GDPR compliance. The KYC and AML capability is described as basic, so organizations with more demanding compliance workflows may need to assess whether it is sufficient.

Fee-shifting and revenue sharing

The zero-fee option passes processing costs to customers through either a flat fee or a percentage. It can lower the business’s direct processing expense, but the added charge may affect conversion or customer satisfaction. Customizable revenue-sharing arrangements are available to financial institutions, software platforms, and marketplaces, with earnings tied to transaction volume and terms shaped around the business model.

Pricing

DreamPay uses paid, custom pricing; no public plan rates, seat allowances, quotas, trial period, or renewal terms are provided. That approach may suit enterprises negotiating an arrangement around volume, payment methods, and revenue sharing, but it makes early budget comparison difficult. The zero-fee model is an operating choice rather than a free plan: customers pay the processing charge selected by the business.

Platforms

DreamPay supports Android, iOS, web, and API integrations. The API emphasis is important for organizations embedding payment and payout flows into core applications rather than adopting a separate merchant-facing app.

Who it's for

DreamPay is aimed at banks and other financial institutions, insurers, software platforms, marketplaces, and large enterprises. It is a strong candidate when private-label presentation, multiple payment and payout rails, reconciliation data, and webhook-driven integration are central requirements. A small business wanting a simple, ready-priced checkout should look elsewhere.

Pros and cons

• Pro: One platform spans recurring and one-time acceptance, payouts, bank transfers, and point of sale, reducing the need to assemble separate payment capabilities.
• Pro: ACH, EFT, real-time payments, virtual cards, Interac e-Transfer, and cheques cover varied payout use cases.
• Pro: APIs, webhooks, and transaction reporting support reconciliation and operational monitoring.
• Con: Custom pricing leaves costs, limits, and commercial terms to negotiation, slowing straightforward comparison.
• Con: Zero-fee processing shifts the charge to customers, which may be unsuitable for price-sensitive audiences.
• Con: Basic KYC and AML tools may not meet organizations needing extensive compliance automation.

Alternatives

Choose Stripe Connect when you want Stripe to set and collect processing fees from connected accounts with no platform fee under its stated arrangement. Checkout.com is worth considering for a registered charity eligible for free processing in supported countries, or for organizations seeking tailored pricing. Pick PayPal Multiparty Payments when PayPal’s complete platform fits and your platform or marketplace can obtain approval.

NMI is another paid option across web, mobile, API, Linux, and Windows. Unipaas suits buyers wanting fees tailored to their business model, transaction volumes, payment rails, and growth plans. WePay publishes card-present and card-not-present rates under its Link Standard beta. Flute Embedded Payments uses partner pricing based on revenue sharing and transaction volume. Stax Connect is a paid alternative with pricing supplied by sales.

For a broader comparison, see Embedded Payments Platforms.

Verdict

Choose DreamPay if your institution, platform, insurer, marketplace, or enterprise needs branded payment acceptance and flexible payouts embedded in software, with API and reporting support. Its main advantage is breadth across payment methods and disbursement rails. Look elsewhere if you need transparent public pricing, a simple merchant checkout, or more than basic built-in KYC and AML controls.