Mass Payment Solution for Real Estate
Trigger the distribution from your backend the moment you approve a split, or upload a CSV from the dashboard with no code. Pay returns to many investors, contractors, or property owners in a single audit-ready batch, multi-currency and reconciled at the line-item level.
Live demo
Pay 248 investors in one click
Upload a CSV (or fire it from your API), validate every IBAN, approve once, and settle the entire batch on SEPA Instant.
Mass payouts
Q2 distribution to investors
distribuciones-q2.csv
248 rows · 18 KB
Live demo
Pay 248 investors in one click
Upload a CSV (or fire it from your API), validate every IBAN, approve once, and settle the entire batch on SEPA Instant.
Mass payouts
Q2 distribution to investors
distribuciones-q2.csv
248 rows · 18 KB
Delivery channels
Delivery channels
Reach your users wherever they already are.
CSV upload
Drop a file from your dashboard.
REST API
Programmatic batches from your backend.
Webhooks per item
Per-beneficiary status pushed in real time.
Recipient emails
Branded breakdown sent to each investor.
Capabilities
-
SEPA Instant at scale
Hundreds of transfers in seconds, fully reconciled.
-
Auto-retry on failure
Exponential backoff for transient bank errors.
-
Tax-ready exports
Modelo 347 + equivalents in other markets.
-
Audit trail
Every batch immutable and exportable.
Integrate in minutes
curl -X POST https://api.urbanpayx.com/v1/disbursements \
-H "Authorization: Bearer $URBANPAY_API_KEY" \
-d '{ "currency": "EUR", "items": [
{ "iban": "ES00...", "amount": 250, "reference": "Q1-DIV-001" },
{ "iban": "ES00...", "amount": 412, "reference": "Q1-DIV-002" }
]}'
Frequently Asked Questions
You provide one batch, by CSV upload or a single API call, with a line per investor that carries their amount, currency, and your internal reference. An authorized operator approves, and the payouts run in parallel as independent transactions, so one failed line never blocks the rest. Each line is reconciled back to your ledger and recorded immutably for audit. Distributing quarterly returns to hundreds or thousands of investors becomes a single reviewed batch rather than a day of one-by-one bank-portal transfers. This mass payout capability is on UrbanPay's roadmap, so the path today is a consultative scoping conversation rather than self-serve onboarding.
The Problem Mass Disbursements Solve
When a crowdfunding platform closes a quarterly distribution to 1,800 investors, or a property manager pays 240 landlords their net rent for the month, the default workflow is brutal: paste IBANs one by one into a bank portal, reconcile amounts, handle errors, and finally try to match the whole thing back against the ledger.
Mass disbursements invert that flow. You upload a CSV (or call the API) with all 1,800 lines. An authorized operator reviews and approves. UrbanPay runs the batch against the right rails and returns a per-line status report.
Anatomy of a Batch
Each line in the CSV carries, at minimum: recipient identifier, IBAN, amount, currency, and your internal reference. You can add tax metadata, project code, or any field you need for downstream reconciliation.
Before execution, UrbanPay validates the structure of every IBAN, checks for duplicates, confirms your balance covers the total, and returns a pre-flight report. Only after your final approval does the batch start — individual payouts run in parallel and are treated as independent transactions (a failure on line 423 doesn't stop line 424).
Multi-Currency Without the Headaches
A pan-European real-estate crowdfunding fund has investors paid in EUR, GBP, CHF, SEK, and NOK. The traditional approach means opening accounts in every currency or eating the hidden FX spread from the issuing bank.
UrbanPay converts each line at the FX rate agreed in your contract, records the rate applied, and deposits in the recipient's local currency. Your operating account stays in a single currency; investors receive in theirs.
Audit Trail and Compliance
For regulated platforms like ECSP (European Crowdfunding Service Provider) or operators running escrow accounts, traceability of investor payouts isn't optional. Every batch is recorded immutably with: who created it, who approved it, what was sent, when each line executed, and what confirmation the bank returned.
The tax export includes the fields needed for 1099 filings (US), Modelo 347 (Spain), and equivalent declarations in other markets — work that typically takes days at year-end becomes a query and a download.
When You Need Mass Disbursements
- •Crowdfunding distributions: income or capital repayment to hundreds or thousands of investors after an exit event. This is the engine behind how platforms automate investor distributions end to end.
- •Net rent to landlords: at managers running third-party portfolios, where every month the landlord receives their share net of expenses.
- •Vendor and contractor payouts: maintenance, cleaning, refurbishments — month-end with dozens or hundreds of invoices.
- •Bulk deposit refunds: at the end of a development cycle when dozens of tenant deposits need to be returned after account verification.
From CSV to Sent in One Session
A typical operator workflow: export the CSV from your system (ERP, property-management tool, spreadsheet), upload it into the UrbanPay dashboard, review the pre-flight report, approve, and come back hours later for the execution report. For larger volumes most teams automate the whole loop via API and receive per-line status webhooks, dropping the results straight into their accounting system.
Other features
A2A Payment Initiation
Collect straight from the payer's bank account, settled in seconds.
See feature →Open Banking
Regulated PSD2 access to bank accounts across 19+ markets.
See feature →Identity Verification
KYC for individuals and KYB for companies in minutes.
See feature →Contract Signing
eIDAS-grade signing chained to onboarding and the first payment.
See feature →Escrow Accounts
Per-project segregated accounts with conditional release.
See feature →Unified Card Processing
Cards as a fallback rail, reconciled alongside A2A.
See feature →