Stripe is a secure payment gateway that allows for online credit card payments within Eventsforce. You must first create an account with Stripe by clicking here.

By default, new events will only allow bookers to request an invoice (pay later). Event managers must enable the option to allow payment by card. The setting can be adjusted to allow the booker to "Request an Invoice", "Pay by Card" or "Select from Either".

This article will cover the following:

Obtaining credentials in Stripe

To connect your Stripe account to Eventsforce you will need a “Publishable key” and a “Secret key”. You can get these keys by taking the steps below:

  1. Log into your Stripe account as a user with Administrator permissions

  2. Select “Developers” on the left hand side

  3. Select “API Keys” under ‘Developers’ on the left hand side

  4. Make note of the “Publishable key” (to be used later)

  5. Click “Reveal live key token” to display the “Secret key” (to be used later)

Note: The “Secret key” is secure and should be treated like a password. You also have the option to “Roll key…” which generates a new key, rendering the previous key invalid. Be sure to update Eventsforce if “Roll key…” is ever used.

Eventsforce setup and configuration

Once you’ve retrieved your credentials, log into your Eventsforce account and select the event that you want to collect online payments for and follow the steps below:

  1. Go to Setup > Finance > Settings

  2. In the 'Payment settings' panel, select "Pay by Card" or "Select from either" to make the Stripe fields editable

  3. Paste the ”Publishable key” and “Secret key” into the corresponding fields in Eventsforce

  4. In the "Organisation name:" field, enter the name you want to appear to the user on the Stripe page (the name of the event is displayed by default)

  5. In the “Description” field, enter any additional description that should appear in Stripe for this payment (ex: the event name). The “Event name” also comes through the metadata to Stripe.

  6. Click “Save”

Creating a test registration

Once the test credentials have been added, we recommend creating a test registration to ensure Stripe is now linked to your Eventsforce event. Follow the steps below:

  1. Ensure there is a price assigned to the ticket you will book

  2. Click the “Preview your website” icon in the top left of Eventsforce

  3. Select a ticket with a fee and proceed to the ‘Checkout’ page

  4. Click the "Pay Now"

  5. The secure Stripe form will appear as a prompt to enter card details

  6. Enter the test card details into the form

  7. Click the "Pay Now" button

You should test multiple scenarios with test card credentials provided by Stripe, including successful and unsuccessful payments to ensure that you are getting the expected results (example: check that the automatic card payment acceptance and failure emails in Eventsforce are sending if active).

Possible outcomes

  • User does not complete the Stripe form and closes the form or the browser window; their registration will not be completed and will therefore not be added to the Eventsforce database as a registration.

  • User's card is declined; a message will be displayed to the user and Stripe will not process the payment.

  • A user enters incorrect card details; Stripe will not process the payment and the field with the incorrect value will be highlighted.

Activating live Stripe account

Once all testing is complete, the last step is to “activate your account”, converting your “Test” Stripe account to a “Live” Stripe account. Follow the steps below to activate your account:

  1. Log into Stripe

  2. Select “Activate your account” on the top left

  3. Enter your business information, personal information, and bank details as required by Stripe

  4. Once your account is “Live”, replace the current test Stripe credentials in Eventsforce with your live “Publishable key” and “Secret key”

Stripe Metadata

Eventsforce passes over certain metadata to Stripe for each payment. The following metadata is included with each payment automatically:

  • Event name

  • Event ID

  • Account name

  • Registration reference

Other articles you may find useful:

Did this answer your question?