Checkout Flow

When an Attendee checks out for an Event, many records are created and updated automatically.

Matching and Duplication

  • Blackthorn Events will attempt to match an existing Contact, Lead, or Person Account by active duplicate rules. By default, we use the out of the box Salesforce Matching and Duplication rules, but we support custom rules as well.
  • If there is a match, the following steps will relate to the existing Contact. If there is not a match, the Contact will be created.

Where does the information go?

  • All of the following records to the logged in the Contact record.

Order of Execution in Salesforce

  1. An Attendee record is created in Salesforce

    • The Attendee record related to the Contact, Lead, or Person Account (from v2.46+) and the Event. Registration Status is set to Confirmed.
  2. Form Elements are processed next.

  3. Invoice & Line Items get created.

    • Invoices
      • An Invoice is created and populates the Contact/Lead/Person account, Status field, Subject Line field, and additional fields as configured.
    • Line Item(s)
      • One Line Item is created for each item in the checkout. One ticket purchase will have one Line Item created, referencing the item purchased, quantity, unit price, and Event.
  4. The Bill to Contact is linked to the Invoice.

  5. The Contact is set on the Payment Method and Transaction.

    • Payment Method (Paid Events)

      • The Payment Method's sensitive information is sent immediately to Stripe and a token is received (PCI compliant fashion, Blackthorn's stack does not store sensitive Payment Method information, such as the card number of banking account/routing).
      • The token along with the rest of the payload (card holder name, address, etc.) is inserted to Salesforce to create the Payment Method. Stripe's response with a valid 'Card ID' or similar Payment Method ID (for other payment methods) is updated on the Payment Method record. The Payment Method Contact is populated.
    • Transaction

      • A Transaction is created with the related Payment Method, populating applicable fields (Currency, Amount, Contact, and additional fields as configured), can be Captured immediately. The response is returned to the Attendee if the Transaction fails. If it's successful, the checkout process continues.
    • Transaction Update

      • The Transaction is updated to reference the Invoice, setting the Payment Status as "Paid".
  6. Event Item purchase records get created.

    • Line Item
      • The Line Item is updated to reference the Attendee record.

Did this page help you?