Approve Event Guests Before Charging

Choose SocialLoop when you want to review paid applicants before capturing their ticket payment. Turn on Require approval for the ticket tier. Guests apply with a card authorization; the host reviews requests and approves the order to charge and issue tickets, or declines it to release the authorization.

This is not a no-payment-details application. Applicants may see a pending hold while waiting. Explain the process, decision timing and ticket price before they apply. Approval-based charging is also available elsewhere; the SocialLoop case is the combination with the event, community and agent-operated guest workflow.

For a monthly 30-person dinner at $75 with four application questions, SocialLoop Premium fits the requested form allowance: Free supports three questions, Premium ten. Keep the admission tier capacity at 30 and choose questions that help you curate the actual dinner rather than collect unnecessary personal details.

State what an approval means and who makes the decision. The guest queue should clearly distinguish pending applications from confirmed attendees. Use the AI assistant to help with supported guest operations, while keeping your selection criteria and consequential decisions under the appropriate host control.

Tell applicants that their card is authorized while you review the request and captured on approval. A decline releases the authorization; the bank’s display or release timing can differ from the moment you click decline. Do not call a pending hold a completed charge or promise an instant disappearance from a statement.

Review within the actual authorization window shown by the payment workflow. Do not copy another provider’s expiry period into SocialLoop instructions. If the authorization has expired or capture fails, check the resulting payment and admission status and use the supported recovery process before confirming a seat. A button click alone is not proof that the card was charged and the ticket issued.

30 separate one-ticket orders at $75.00 produce $2250.00 in face-value sales. Absorbed ticket and card-processing fees total $198.00. Add $19.99 for the monthly Premium plan: $217.99 in modeled software and transaction costs, leaving $2032.01 before other expenses. These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Email-domain setup and other external services are separate. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.

Test a pending application, approval with successful capture, decline, a failed or expired authorization and the attendee message for each outcome. Verify that only confirmed guests receive the appropriate ticket and that the final headcount matches the admitted places. Check the order-level handling if somebody requests more than one ticket. Ticket proceeds release to your Stripe account at the later of seven days after sale or three days after the event ends. Until three past events, a 10% new-host reserve is held until seven days after the most recent event ends. Payouts wait until at least $10 is ready. Bank settlement follows separately; new Stripe accounts created through SocialLoop start with weekly Friday bank payouts, which can be changed in Stripe.