Payment collection and merchant lending under your own brand
D-PAY is the white-label platform from Determinds through which banks and non-bank financial institutions offer payment collection and merchant lending under their own brand. Your institution launches it within twelve weeks, with no upfront investment, and pre-approves merchant loans from the payments it already collects.
01 Why D-PAY
Four advantages D-PAY brings to your institution
Your brand on every surface
Merchants, partner providers, and your own teams work in a platform that carries your institution's brand, from the merchant portal to emails and invoices. Your team sets the logo, colors, and English and Arabic templates in the white-label studio and sees the portal update in a live preview.
Live within twelve weeks
A standard deployment goes from contract to go-live within twelve weeks, with around forty person-days of integration on your side against one integration surface.
Payments and lending in one system
Because collection and lending share one platform, your institution pre-approves loans from each merchant's transaction history, and merchants apply in a few clicks from the same portal they use to get paid. Repayment comes from an agreed holdback on incoming payments.
No upfront investment
Your institution launches D-PAY with no upfront investment or cost. D-PAY is charged as a fixed fee plus a percentage of each transaction, with a minimum guarantee.
02 The business case
Acquiring succeeds on the operations around the gateway
Payment processing is one part of a successful acquiring business, and the most familiar one.
The larger part is the operational machinery around it: merchant onboarding and know-your-customer checks at volume, pricing that serves a small business and an enterprise merchant from the same platform, support, dispute handling against scheme deadlines, and reporting a regulator will accept. D-PAY delivers that machinery, so your institution can serve high-volume small merchants with the same strength it brings to credit.
Payment collection brings your institution three sources of value.
| Fee income | Annuity revenue on every merchant transaction, growing with merchant volume. |
|---|---|
| Credit data | Transaction volume, settlement regularity, and dispute behavior, the best available signal on a small business, so your payment flow becomes your lending flow. |
| Merchant deposits | For a bank, low-cost funding, because a merchant collecting through the bank keeps a current account with it. |
03 Payment collection
Payment collection for your merchants, from application to payout
D-PAY takes each merchant from application, through maker-checker approval at your institution, to the service offer the merchant accepts before activation, covering fees, pricing tiers, and payment terms. Your team sets the fees for each merchant, including tiered pricing.
Merchants accept payments by card, digital wallet, QR code, and payment link, and through local services such as Meeza and Fawry. In their own portal, they track transactions, manage refunds and disputes, view payouts, and download reports.
New merchant · service offer
Illustrative| Item | Detail | Status |
|---|---|---|
| Application | Business details and documents | Submitted |
| eKYC | Electronic identity check | Verified |
| Institution approval | Maker-checker control | Approved |
| Fees | Tiered pricing | Proposed |
| Payment methods | Cards, wallets, QR, links, Meeza, and Fawry | Selected |
| Payout schedule | As agreed with the merchant | Proposed |
| Merchant acceptance | Service offer in the portal | Awaiting merchant |
Maker: onboarding officer · Checker: risk and compliance
Send offer to merchant04 The merchant portal
A merchant portal for getting paid, tracking money, and borrowing
Each merchant works in one portal under your institution's brand, in Arabic or English, from the first application to loan repayment.
Simple onboarding
Merchants apply online, submit their business details and documents, and track their application through to activation.
Clear service offers
Merchants review your institution's proposed fees, pricing tiers, and payment terms, and accept them before activation.
Multiple payment options
Merchants collect payments through cards, digital wallets, Meeza, Fawry, and buy now, pay later providers such as valU, Sympl, and Contact.
Payment collection tools
Merchants create payment links, QR codes, and invoices to send to their customers.
Transaction tracking
Merchants see the status of each payment, their sales history, and their customers' payment activity.
Payout visibility
Merchants track the money due to their business, payout dates, fees, and deductions.
Refunds and disputes
Merchants issue refunds and respond to payment disputes from their portal.
Reports and insights
Merchants follow their sales trends, payment performance, and cash flow.
Access to business loans
Merchants receive and review financing offers from your institution, based on their payment history and eligibility, and apply in a few clicks.
Automatic loan repayment
Merchants repay through an agreed share of incoming revenue, and track each deduction and their remaining balance.
Fraud protection
Fraud detection from Visa's ecosystem, including Cybersource, screens each payment before it is approved.
Integration and language support
Merchants connect payments to their website or business systems through plugins and APIs, and use the portal in Arabic or English.
05 Merchant lending
Merchant lending built on each merchant's own transaction history
D-PAY gives your institution each merchant's transaction history and incoming revenue, so your credit team can assess repayment capacity, pre-approve suitable loan amounts and terms, and present the offer in the merchant portal. The merchant applies in a few clicks, and each loan passes maker-checker approval at your institution.
Installments are collected automatically through an agreed holdback on incoming payments, and the remaining funds are paid out to the merchant. Lending and repayment move with the merchant's own sales.
Daily settlements with automatic repayment
IllustrativeEach day's settlement goes to the merchant after an agreed holdback repays the loan.
From payments to a working-capital loan
- 01
Payments flow in
Each merchant's payments are collected through D-PAY.
- 02
Eligibility builds
From collected volume, settlement regularity, dispute ratio, refund behavior, and history.
- 03
Pre-approved offer
Your institution pre-approves a loan at the limits, tenor, and pricing it sets.
- 04
Apply and approve
The merchant applies in a few clicks, and the loan passes maker-checker approval.
- 05
Automatic repayment
An agreed holdback on incoming payments, with the rest paid out to the merchant.
06 Technology, security, and compliance
Built with Visa's ecosystem, with the controls a regulated institution needs
D-PAY is built with Visa's ecosystem, covering Cybersource payment processing, fraud detection, and electronic know-your-customer checks (eKYC). Determinds built the platform around it, with approval controls, audit trails, and reporting designed to support your regulatory requirements, and D-PAY integrates with Mastercard when your institution requires it.
Under your brand, end to end
What your merchants and teams use
Merchant portal
Payments, payouts, and loan offers
Institution back office
Operations, risk, and compliance
White-label studio
Your logo, colors, and templates
Local rails
Meeza QR, Fawry, and buy now, pay later
D-PAY, built and owned by Determinds
Merchant lifecycle · pricing engine · merchant lending · analytics and regulatory reporting · hosted in Egypt
Visa's ecosystem, embedded and licensed through Determinds
Payment processing
Cybersource, one certified connection
Scheme connectivity
Visa, Mastercard, American Express, and Meeza
Tokens and wallets
Apple Pay, Google Pay, Samsung Pay, and Click to Pay
Fraud, disputes, and eKYC
Screening, one dispute inbox, and identity checks
Your existing systems
Core banking
Card management
Data warehouse
Security event platform
Built and owned by Determinds
- The orchestration core, and the single integration surface your teams work against
- Merchant onboarding and lifecycle: application, document upload, maker-checker approval, hierarchy and multiple branches, suspension and termination, with an immutable audit trail on every record
- Pricing engine with blended, interchange-plus, and tiered rates, a rate card for each card scheme, and the service offer each merchant accepts
- Back office for your operations, risk, and compliance teams, and sub-portals for payment service providers, each limited to its own merchants
- Payment acceptance beyond cards: QR to the Meeza specification with local settlement reconciliation, payment links, bulk links, and electronic invoicing
- Local payment rails: bill payments through Fawry, Aman, and Masary, and installments through valU, Sympl, and Contact, with one eligibility check across the three providers
- Merchant lending: eligibility from collected volume, settlement regularity, dispute ratio, refund behavior, and history, pre-approved offers in the merchant portal, maker-checker approval, and repayment through an agreed holdback
- Loyalty programs, including programs shared across several merchants
- Consolidated analytics, operational dashboards, and regulatory reporting in Central Bank of Egypt formats
- Arabic-first screens with right-to-left layouts, local formats, and branded email and SMS
- Integration with core banking, card management, the data warehouse, your security event platform, and the general ledger
- A white-label studio where your team uploads a logo, picks brand colors, and edits English and Arabic templates while the merchant portal updates in a live preview
Visa's ecosystem, embedded and licensed through Determinds
- Cybersource payment processing and gateway, including hosted checkout
- Scheme connectivity across Visa, Mastercard, American Express, and Meeza from a single certified connection
- 3D Secure 2.1 and 2.2, with risk-based frictionless routing and exemption rules
- Tokenization with gateway and network tokens, updated automatically when an issuer reissues a card
- Digital wallets: Apple Pay, Google Pay, Samsung Pay, and Click to Pay, switched on for each merchant
- Fraud detection with machine-learning scoring, rules for velocity, location, and device fingerprinting, block and allow lists, and a review queue
- Disputes in one inbox across Visa, Mastercard, and American Express, with pre-dispute resolution through Visa Rapid Dispute Resolution, the Cardholder Dispute Resolution Network, and Order Insight
- Electronic know-your-customer checks (eKYC)
Every embedded component reaches your institution and your merchants through D-PAY, under one contract and one accountable team.
The processing core is swappable
If your institution is a Mastercard principal, the processing core can be served through Mastercard's gateway, with the D-PAY layer unchanged. Our team scopes each substitution with your institution before quoting a timeline.
07 Deployment in detail
Deployment, pricing, and compliance
| Deployment | Within twelve weeks from contract to go-live, with around forty person-days of integration on your side, for a bank or for a non-bank institution with a sponsoring bank. |
|---|---|
| Pricing | No upfront investment. D-PAY is charged as a fixed fee plus a percentage of each transaction, with a minimum guarantee. |
| Hosting | D-PAY is hosted in Egypt, under arrangements compliant with Central Bank of Egypt requirements. |
| Processing core | PCI DSS Level 1 and SOC 2 Type II through Visa Acceptance Solutions, with Cybersource's published service levels: 99.99% monthly platform uptime, a median authorization response under 500 milliseconds, and Visa network capacity of around 8,000 transactions per second. |
| Security standards | Every D-PAY component is developed to recognized security standards, including PCI DSS, SOC 2, and ISO 27001. |
| Acquirer of record | Your institution, or the bank that sponsors it, remains acquirer of record under its license. Accepting Mastercard, American Express, and Meeza requires acquirer principal membership, held by your institution or its sponsoring bank. |
08 Frequently asked
Questions about D-PAY
Questions institutions ask before a deployment starts.
What is D-PAY?
D-PAY is the white-label platform from Determinds through which banks and non-bank financial institutions offer payment collection and merchant lending under their own brand. It is built with Visa's ecosystem, launches within twelve weeks, and requires no upfront investment.
What does it cost to launch D-PAY?
Nothing up front. D-PAY is charged as a fixed fee plus a percentage of each transaction, with a minimum guarantee.
Can a non-bank financial institution offer D-PAY to its merchants?
Yes. Your institution, or the bank that sponsors it, remains acquirer of record under its license, and the deployment estimates are the same as for a bank.
How do merchants get a loan through D-PAY?
Your institution pre-approves loan amounts and terms from each merchant's transaction history and incoming revenue, and the merchant applies in a few clicks from the portal. Installments are collected through an agreed holdback on incoming payments, and the remaining funds are paid out to the merchant.
Which payment methods can our merchants accept?
D-PAY accepts Visa, Mastercard, American Express, and Meeza cards through hosted checkout, QR codes, payment links, and electronic invoices, alongside Apple Pay, Google Pay, Samsung Pay, Click to Pay, bill payments through Fawry, Aman, and Masary, and buy now, pay later through valU, Sympl, and Contact. Mastercard, American Express, and Meeza require acquirer principal membership, held by your institution or the bank that sponsors it.
How long does a deployment take?
Within twelve weeks from contract to go-live, with around forty person-days of integration on your side against one integration surface. An early deployment gets the founders and the engineers who wrote D-PAY.
How is D-PAY different from a payment gateway?
D-PAY embeds a payment gateway and adds merchant onboarding, your own back office, local payment rails, merchant lending from your transaction data, and an Arabic-first merchant experience. Determinds built that layer.
Can the processing core be changed?
Yes. The processing core is swappable, so a Mastercard principal can be served through Mastercard's gateway, with the D-PAY layer unchanged. Our team scopes each substitution with your institution before quoting a timeline.
Can D-PAY be hosted in Egypt?
Yes. D-PAY is hosted in Egypt, under arrangements compliant with Central Bank of Egypt requirements.
D-PAY
Work with the founders on an early D-PAY deployment
An early deployment gets the founders and the engineers who wrote D-PAY, working against one integration surface on your institution's side.