Skip to main content
Customer Leads helps you collect visitor details before checkout and see when a lead becomes a paying customer.

​
Set up lead capture

  1. In Platform, open Tools → Customer Leads.
  2. Select API endpoint to view and copy the lead submission URL.
  3. Select Webhooks.
  4. Add each website origin that may send leads directly from a browser.
  5. Select Save configuration.
  6. Copy the generated API keys and store them securely. Keys are only shown when they are created or rotated.
Use the publishable key for browser submissions from an allowed origin. Keep the secret key in a secure private integration and never expose it in browser code. See the Customer Leads API reference for request fields, authentication, and examples.

​
Match leads to payments

Under Paid conversion, select the transaction applications that should mark a lead as paid. Enable sandbox transactions only when you want test payments to update leads. Each lead must use the same session identifier as the related Paysight checkout:
  • Send the value to the Customer Leads API as session_id.
  • Send the same value to Card Submit as partnerSession, or use it as the Widget session ID.
  • Keep the value at 50 characters or fewer.
When a successful configured transaction matches that session, the lead status changes from lead to paid and its payment details become available in Platform.

​
Receive paid-lead notifications

You can send a notification to your system whenever a lead is marked paid:
  1. Open Customer Leads → Webhooks.
  2. Under Paid-lead webhook, enable webhook delivery.
  3. Enter your HTTPS endpoint.
  4. Save the configuration.
  5. Copy the generated signing secret and store it securely.
Paysight sends a customer_lead.paid event containing the lead and matched payment details. Your endpoint should return a successful 2xx response after accepting the event. See the Customer Leads API reference for the webhook payload, signature format, and delivery behavior.