Payment Integration

Connect your payment provider to Boei so a successful payment marks the matching contact as a customer and moves open deals to Won.

Payment integrations are available during the trial and on the Growth plan and above.

How to get there: Open Website settings → Integrations → Payments. Each integration belongs to one website and one deals pipeline. You can create multiple integrations per website.

What happens after a payment

  1. Boei verifies the request using the provider's authentication method.
  2. Boei reads the customer email from the event. When needed, it securely retrieves the payment or customer from the provider API.
  3. The contact for the selected website is created or marked as a customer.
  4. If the event references a Boei deal, that deal is moved to Won. Without a reference, Boei only moves a deal when exactly one open deal matches the contact, website, and pipeline.
  5. The result appears in the webhook's delivery log.
  6. If enabled, Boei sends an email when at least one deal was moved to Won.

Repeated provider events are safe. Boei deduplicates provider event IDs. Mollie payment callbacks are checked again because the same payment ID can move from pending to paid.

Provider setup

Create the integration in Boei first, then copy its unique endpoint URL into your payment provider.

Stripe

  • Event: invoice.paid, checkout.session.completed, or checkout.session.async_payment_succeeded
  • Credential in Boei: the endpoint signing secret (whsec_...)
  • Stripe signs every request. Boei verifies the signature before accepting it.

For Checkout, ensure the session contains customer_email or customer_details.email. Stripe invoices should contain customer_email.

Mollie

  • Event: payment status update
  • Credential in Boei: a Mollie API key
  • Mollie's webhook contains the payment ID. Boei retrieves that payment from Mollie and only continues when its authoritative status is paid.

Boei first looks for an email in the payment's billing address or metadata. If needed, it retrieves the linked Mollie customer.

Paddle

  • Event: transaction.completed
  • Credentials in Boei: the endpoint secret key and an API key
  • Choose Live or Sandbox to match the Paddle account.

Boei verifies the Paddle-Signature. If the event contains a customer ID but no email, Boei uses the API key to retrieve the customer.

Chargebee

  • Event: payment_succeeded
  • Credentials in Boei: a Basic Auth username and password that you choose

Configure the same username and password on the Chargebee webhook. Boei reads the customer email from the event's customer object.

Shopify

  • Topic: orders/paid
  • Credential in Boei: your Shopify app client secret

Boei verifies the X-Shopify-Hmac-SHA256 signature and reads the email from the paid order or its customer.

Custom JSON

Use Custom JSON for your own billing system, an automation tool, or a provider that is not listed. Send the secret as a bearer token:

Authorization: Bearer YOUR_SECRET
Content-Type: application/json

Use this canonical shape when you control the sender:

{
  "id": "event-123",
  "type": "payment.succeeded",
  "occurred_at": "2026-10-06T12:30:00Z",
  "customer": {
    "id": "customer-456",
    "email": "customer@example.com",
    "name": "Jane Doe"
  },
  "payment": {
    "id": "payment-789",
    "amount": "49.95",
    "currency": "EUR"
  },
  "deal": {
    "id": "BOEI_DEAL_UUID"
  }
}

Required fields:

  • id: a unique event ID used for deduplication.
  • type: payment.succeeded, customer.paid, or invoice.paid.
  • A customer email, preferably in customer.email.

Recommended fields:

  • customer.id: the customer ID in the sending system.
  • payment.id: the payment or transaction ID in the sending system.
  • payment.amount and payment.currency: the amount in major currency units, such as 49.95 and EUR.
  • deal.id: the Boei deal UUID or numeric ID when the payment belongs to a known deal.
  • occurred_at: an ISO 8601 timestamp.

For flexible integrations, Boei also accepts event or event_type instead of type, top-level payment fields, and customer data under data.customer. If no known email field is present, Boei checks every string field whose complete value is an email address and uses it when exactly one unique address is found. It does not extract addresses from sentences or other text. Repeating the same address is fine. If multiple different addresses are found, the delivery is marked Needs attention instead of guessing.

When deal.id is absent, Boei moves a deal to Won only if exactly one open deal matches. Multiple open deals are marked Needs attention so Boei never closes the wrong deal.

Delivery statuses

  • Processed: the contact was updated. The log says whether deals moved to Won.
  • Ignored: the event was valid but was not a supported completed-payment event.
  • Needs attention: payment was recognized, but the customer email or matching deal was ambiguous.
  • Failed: the provider lookup or processing failed. Boei retries temporary failures automatically.

Provider credentials and stored webhook payloads are encrypted. They are never returned by the settings API. Delivery payloads and their event records are automatically deleted after 90 days. Unfinished setup drafts without credentials or deliveries are removed after 24 hours.

Made with ProductLift