Configuring Offline Payments for Your Events

There are multiple ways you can accept payments using the Event Genius Pro plugin. One of these methods is using offline payments, which allows users to complete their registration for an event on your website but then pay offline.

This allows users to pay at the door of an event, and allows you to accept physical payments such as checks or cash, or to accept digital payments in person via Venmo, a POS terminal, or any other in-person payment method.

Configuring Offline Payments

To configure offline payments:

1. Go to the plugin’s Payments settings page: Events > Settings > Payments.

2. In the Payment Methods section, enable the toggle next to the “Offline” option.

3. Here you can also change the order of how the payment methods are displayed when users are buying tickets on your site. The first payment method is shown first in the list of options for users at checkout.

4. To configure the options for the Offline payment method, click the “Configure” button next to it.

5. Here you can customize a variety of settings to configure how the Offline payments method is displayed to users. The main settings are described below.

Checkout – Payment Option Label

This is the label used at the checkout to describe the payment method. A user clicks on this label to select the Offline payment method.

Checkout – Payment Option Description

This text is shown under the label to describe what the Offline payment method does.

Checkout – Button Text

This is the text on the button displayed for the user to complete their Offline payment.

Checkout – Additional Instructions

This text is displayed after the user selects the Offline payment method and is used to describe what will happen next. This setting allows for full WYSIWYG text or HTML to allow you to format the text or add links. It also allows you to insert dynamic placeholder data.

After Confirmation – Registration Status

This allows you to choose whether registrations should be marked as confirmed or pending immediately after the registration is submitted using the Offline payment method.

A “pending” registration does not receive the confirmation email for the event automatically (it can be sent by an event admin later). This is ideal for events that require payment to be completed before the person should expect to attend the event. Consider the payment flow of a person choosing to pay offline, the person sends a check or sends a Venmo payment, the event admin confirms receipt and then marks the registration as “confirmed” and sends the confirmation email for the event to that person.

A “confirmed” registration will receive the confirmation email for the event automatically. This is ideal for events that are only collecting a physical payment at the location of the event as well as events where the person registering can choose to pay via Stripe or PayPal or wait to pay the day of the event at the physical location of the event.

Both choices can still be used with the emailed payment instructions. If you need to include more information about the event or about payment without wanting the person to be considered a confirmed attendee, you can use the payment instruction email to make this clear to people registering.

After Confirmation – Payment Success Message

Here you can configure the success message after the registration is submitted using the Offline payment method. It’s a full WYSIWYG field which supports images, links, HTML, and dynamic placeholders.

Email Settings

The email settings allow you to customize messages for both the Payment Instruction email which is sent to the registrant immediately after registering using the Offline payment method, and the Pending Notification email which is sent to the event admin to let them know about the offline payment submission.

If your event admin needs to take action whenever someone chooses the “offline” payment type, the admin pending notification email can be a useful alert for these next steps.

You can customize the subject and content for both emails, including dynamic placeholder data in any of the fields.