Three days after a sold-out night at a 150-seat club in Mouraria, the artist is still waiting. Nothing failed. The promoter still needs to match the door count, remove the venue guarantee and sound engineer's fee, work out the platform percentage, and send the transfer. Doing that by hand takes time, and creates leaks.
We built Membrz to make payout the finished step of a ticket sale, rather than a separate job for later. Here is the route the money takes, step by step, from a ticket purchase to the artist's account.
How payment is captured
On Membrz, every ticket and merch purchase uses Stripe as payment processor. Stripe authorizes cards, handles 3DS2 authentication for EU transactions required by PSD2, and captures the funds. Because Stripe is PCI DSS Level 1 certified, Membrz does not handle or store raw card data. Stripe carries the card-handling liability and compliance work, not us or the organizer.
At ticket checkout, Stripe authorizes and captures in one step, rather than holding funds before capture as hotels and rentals often do. The payment then remains in Stripe's settlement account through the normal T+2 card-settlement cycle.
Across EU SEPA territory, card-not-present payments generally settle within two business days. Timing varies by card network and issuing bank, but T+2 is the practical assumption for most Visa and Mastercard payments in Portugal and the EU.
The accounting step
After capture and before payout, Membrz applies the fee and split rules the organizer set before launch. This is not a manual calculation after the event. Up front, the organizer defines each percentage, any flat fee taken first, and the platform fee for that pricing tier.
When the organizer completes the event, or the automated end-of-event trigger fires, Membrz works out each stakeholder's net amount from the final ticket and merch revenue. Stripe deducts the platform fee first, before disbursement. The balance then follows the split rules.
That is the key distinction between accounting and payment software. A spreadsheet can calculate the figures, but cannot send the money. Membrz sends each payout without the organizer starting a transfer for every recipient.
SEPA payout and bank transfer mechanics
After calculating the split, Membrz sends payouts through Stripe Connect. Every named recipient, artist, venue, sound engineer, or anyone else, needs a connected bank account. During event setup, the recipient supplies an IBAN, Stripe performs a light identity check, and the account is verified for later payouts.
Recipients in the SEPA zone, covering 36 countries including every EU member state and several non-EU European countries, receive bank transfers as SEPA Credit Transfers. Standard SEPA settles within one business day. Instant SEPA (SCT Inst) arrives in seconds, although not every Portuguese bank supports it for every account type.
In practice, an event closed on Saturday night gets its payout calculation immediately. Bank credit depends on Stripe's transfer batch and the receiving bank's handling of the inbound SEPA message. For most recipients with a Portuguese account at a major bank, the funds arrive Monday or Tuesday.
What delays a payout
We will not pretend every payout is smooth. A few causes repeatedly create delays.
The usual cause is incomplete onboarding. If an artist skips the IBAN step or enters the wrong account number, the bank rejects the payout, with SEPA return codes arriving days later. Membrz shows failed payouts in the organizer's dashboard, but someone must fix them. Our advice: have every split recipient connect a bank account before launch.
Refunds are another source of delay. Stripe keeps a reserve for events carrying refund risk, usually until after the event date. If you sell 200 tickets with a 14-day refund policy, part of the settlement may stay held until the event and refund window end. This is standard marketplace payment behavior, not specific to Membrz.
New organizers and large initial events make up the third case. Stripe may manually review payouts above certain thresholds. That is Stripe's fraud prevention, outside Membrz's control. Most organizers clear the review after their first or second event on the platform.
What the artist sees now
Before tools like Membrz, an independent artist might get a WhatsApp message three days after a show: "Hey, we ended up with X, your cut is Y, sending now." The figure might be correct, or the organizer might have missed a bar buyout taken off the top by the venue. Often, the artist accepted it because the actual ticket count was invisible.
A digital ticket trail timestamps and records every sale. The artist sees the ticket count, tier, and gross revenue, while the confirmed split agreement sits in the same dashboard. There is no WhatsApp reconciliation afterward because the figures are already matched.
This does not make every post-show conversation easy. Late at-door cash sales still need manual entry, last-minute comps can alter the count, and a sound engineer paid in cash that night may need removing from the digital split. Those edge cases remain, but they sit on accurate data rather than a reconstruction based only on memory and trust.
What Membrz does not do
Membrz is not a payment institution, bank, or custodian. Ticket revenue runs through Stripe's infrastructure. Outside the payment processing window, Membrz does not hold funds for organizers or artists. It cannot offer interest or banking services, or serve as a formal financial intermediary under EU payment services regulations.
For large-sum events, or organizers needing formal receipts and VAT invoices for venue payments, Membrz routes the payment while the organizer remains responsible for the required fiscal documents under Portuguese and EU tax law. Membrz covers split calculation, payout disbursement, and dashboard visibility. The organizer still owns the legal and fiscal framework.
We cover the VAT questions for Portuguese creators in another Backstage piece, including the rules for selling digital tickets or downloads to buyers across the EU.