Dual invoicing, automated
In a marketplace, every transaction is two fiscal operations: the professional invoices the customer and your platform invoices the commission to the professional. BeeL. emits both with Verifactu from your payment webhook.
7 days free · no card · Unlimited sandbox · Native idempotency
Two invoices, zero friction
Every transaction in your marketplace generates two distinct commercial relationships that need independent fiscal documentation. BeeL. handles both without complicating your code.
Dual invoicing from your webhook
One call for the professional-to-customer invoice, another for the marketplace-to-professional commission invoice. Both in parallel from your backend — latency is negligible.
Built-in idempotency
If Stripe retries the webhook, you don't duplicate invoices. Idempotency-Key = transaction_id returns the original invoice. Safe retries with no side effects.
Guaranteed Verifactu compliance
Both invoices are automatically registered with the AEAT, with chained hash, official QR and verifactu.status.updated webhook. Real compliance, not marketing.
One API key per fiscal entity
Each professional invoices with their own BeeL. account and API key. Your marketplace uses another for commissions. Clean segregation, auditable and legally correct.
Arbitrarily complex commissions
Flat percentages, volume tiers, promotional discounts, per-category variable commissions. You compute the amount and send it to BeeL. The API doesn't impose business rules.
Real scalability
10 transactions or 10,000 a day, the operational cost of invoicing stays the same. The API is built for volume and rate limits scale with your plan.
Two POST /invoices in parallel
From your webhook handler, fire both invoices in parallel with Promise.all (Node), asyncio.gather (Python) or goroutines (Go). Sub-second latency, full compliance.
Remember: each call uses the API key of the corresponding fiscal entity (professional vs marketplace).
How the integration works
A simple flow that hooks into your payment system and your order management. You can ship it in a morning.
- 1
Customer books a service on your platform
Your app records the transaction with customer, professional and breakdown. You calculate your commission per your model and store IDs for customer, professional and order.
- 2
The payment gateway confirms the charge
Stripe, PayPal or your processor fires the successful payment webhook. Your backend verifies the signature, marks the order as paid and prepares the data for both invoices.
Node.js - 3
Both invoices are generated automatically
One invoice from the professional to the end customer for the service. Another from the marketplace to the professional for the commission. Each company uses its own API key — BeeL. issues both in parallel.
Node.js - 4
PDFs delivered automatically
BeeL. emails both PDFs: the customer gets the service invoice, the professional gets the commission invoice. Sequential numbering and Verifactu QR on both.
- 5
Reporting and reconciliation
GET /invoices with filters by date, customer and status feeds your commission dashboard, your accounting and the monthly reports you hand to your accountant.
