# Integrations

Section: Settings & Integrations · Page: https://artsvp.com/docs/settings/integrations

(Plans: All plans) (Access: Admins only)

ARTSVP connects to the systems you already run in a few distinct ways: Stripe
for money, the API and webhooks for your own software, Meta Pixel and Google
Tag Manager for your analytics, and CSV exports for everything else.
Organisation admins manage all of these settings.

## Stripe: payouts and terminals

- **Payouts** (**Settings** → **Payouts**), connect a Stripe account once and
  revenue from paid tickets is paid out to it on Stripe's schedule. The page
  shows connection health, your Stripe balance, and recent payouts. Guests pay
  by card, or with Apple Pay and Google Pay on the phones and browsers that
  support them: those buttons appear at checkout on their own once your Stripe
  account can take payments. The only action on a connected account is **Manage
  in Stripe**, which opens Stripe's own dashboard. To switch to a different
  Stripe account, contact ARTSVP support.
- **Terminals** (**Settings** → **Terminals**), set up Stripe card readers to
  sell tickets and take payment in person, and check guests in at the same
  time. Terminals need Payouts connected first.
- **Email receipts to guests** (**Settings** → **Payouts**): Stripe emails a
  receipt after each successful payment. Switch this off and Stripe sends
  neither the receipt nor its refund notifications. Your confirmation email
  still goes out, and on paid bookings it includes an order summary with line
  items, tax, and the total. The setting appears once your Stripe account is
  active.

### Supported card readers

ARTSVP works with two Stripe Terminal reader models:

- **Stripe BBPOS WisePOS E**
- **Stripe Reader S700**

No other readers are supported at this time.

### Setting up a card reader

1. **Connect Payouts first**: terminals need an active Stripe account.
   Go to **Settings** → **Payouts** and connect one if you haven't already.
2. **Create a reader location**: open **Settings** → **Terminals**. If you
   haven't set one up, you'll see a form asking for the address where your
   readers will be used. The location must be in the same country as your
   Stripe account.
3. **Register your reader**: once the location is saved, use the **Add a
   reader** form. Enter the pairing code shown on the reader's screen (it
   looks like three words, for example *apple-grape-orange*) and give the
   reader a label so you can tell it apart from others.

The reader appears in your list once registered. The page shows how many of
your readers are online and ready.

### What the reader does

The reader takes card payments that you send to it from ARTSVP. It does not
show a ticket menu, and guests cannot browse or buy tickets on the device
itself: every payment starts in ARTSVP, and the reader completes it.

### Taking payment at check-in

The reader appears in two places, depending on whether the booking already
exists.

**Adding a walk-in with payment (Add Guests)**

When you add a walk-in from the guest list and the booking has a balance due,
the payment step offers **Take payment now**. Choose that option and select a
terminal from the dropdown (only online readers appear). The booking is created,
the payment is sent to the reader, and once the guest taps or inserts their card
and the payment completes, the booking is marked as paid automatically.

**Taking payment on an existing unpaid booking**

Open the booking page for a guest who owes money (an unpaid walk-in, or someone
whose online payment did not complete). In the **Payment** card, click
**Take payment**, then select a terminal. The reader takes over, and the booking
is marked as paid once the payment completes.

**If the guest cancels or the reader times out**

The payment is cancelled and the booking stays unpaid. Return to ARTSVP and
send the payment again from the booking page, or use **Mark as paid** if the
guest paid another way.

**Free-only events**

Events with only free tickets never offer the card reader, because there is
nothing to pay.

## API and webhooks (Plans: Expert)

Under **Settings** → **Developer**, the Expert plan opens ARTSVP to your own
software:

- **API Authentication** holds the single token your systems share against the
  ARTSVP REST API: events, bookings, invitations, and more. See the
  [API overview](https://artsvp.com/docs/api/overview).
- **Webhooks** notify your systems when bookings and events change. Register an
  endpoint and choose which events it receives. See the
  [API overview](https://artsvp.com/docs/api/overview#webhooks).
- Events can carry **resource tags** (set per event in its Developer settings
  tab) to categorise them for API calls.

The token is shown once when generated. Store it safely, because regenerating
it stops the previous token immediately.

## AI apps

Claude, ChatGPT and other AI apps can read your events, collections and
bookings, so you can ask about your programme in plain words. A connected app
is read only, and sees what the person who connected it sees. It is in beta:
see [AI Apps](https://artsvp.com/docs/settings/ai-apps).

## Analytics and tracking

Organisation admins connect a **Facebook Meta Pixel ID** and a **Google Tag
Manager Container ID** under **Settings** → **Developer**, in the **Tracking**
card. You can use one, the other, or both. Container IDs look like
*GTM-XXXXXXX*. Click **Save** after you add or clear a value.

Tracking loads on your public booking pages only after a guest accepts
the cookie prompt (**We value your privacy**). **Accept All** loads the pixel
and container; **Essential Only** loads neither. One thing to be aware of:
that consent step will impact your conversion rates.

A paid event loads tracking automatically once an ID is saved. A free event
stays off until you switch **Enable Tracking Pixels** on the event's
**Settings** → **Developer** tab.

Google Tag Manager can fire Google Ads conversions and other tags from the
events ARTSVP sends: *consent_accepted* when the guest accepts cookies,
*begin_checkout* when they start payment, and *purchase* when the booking is
confirmed. Other tags you manage in GTM, not by pasting a script into ARTSVP.

Clear both IDs and the cookie prompt no longer appears, because there is
nothing to load.

## CSV in and out

- **In**: contacts, invitation recipients, and
  [barcode pool](https://artsvp.com/docs/settings/barcodes) values import from CSV.
- **Out**: guest lists, contacts, and the mailing list export to CSV, ready
  for your CRM or newsletter tool. See
  [Reporting and exports](https://artsvp.com/docs/reference/reporting-and-exports).

CSV exports are point-in-time files; when another system needs ongoing updates,
reach for webhooks or the API instead.

## Working with a CRM

ARTSVP does not need to replace the CRM your team already knows. A common
setup: run invitations, bookings, and check-in on ARTSVP, then export guest
activity (or receive it live by webhook) into the CRM where the rest of your
collector relationships live.

---

Keep reading: [API overview](https://artsvp.com/docs/api/overview) ·
[Reporting and exports](https://artsvp.com/docs/reference/reporting-and-exports) ·
[Billing and credits](https://artsvp.com/docs/settings/billing-and-credits)

---