TicketSocket clients can offer purchase protection to attendees using Protect Group's Refund Protect service. This provides customers with peace of mind while enabling new revenue opportunities for event organizers.

✅ Prerequisites

Before activating the integration, ensure the following steps are complete:

1. Onboard with Refund Protect directly via Protect Group.
    
2. Sign necessary agreements and complete setup via GoCardless for automated billing.
    
3. Obtain these credentials from Refund Protect:
    
   • Client ID (Universal)
      
   • Secret (Universal)
      

Vendor Code (Site-specific — each event site requires a unique one)
 

🔧 Enabling Refund Protect in TicketSocket

1. Navigate to Admin Dashboard.
    
2. Go to Integrations Marketplace.
    
3. Locate the “Purchase Protection” block.
    
4. Toggle it to Enable.
    
5. Choose Refund Protect from the list of vendors.
    
6. Enter the required credentials:
    
   • Client ID (shared)
      
   • Secret (shared)
      
   • Vendor Code (unique per site)
      

⚠️ Important: Vendor Codes must be unique per site. Using the same code across multiple sites can cause failures in link generation due to duplicate order numbers.

🧪 Testing Mode

If testing, you may see a development mode toggle. This option is not visible in live environments and should only be used for QA or dev sites.
 

🛍️ Frontend Experience

When a customer books a ticket:

• A widget appears offering Refundable vs. Non-Refundable options.
   
• If enabled, the system dynamically calculates the protection fee based on customer-specific terms.
   
• The cart updates to include a “Refund Insurance” line item.
   

📧 Refund Claim Flow

After purchase:

1. The customer receives a receipt email from TicketSocket.
    
2. A refund link may either appear directly in this receipt or be sent separately by Refund Protect (this depends on current deployment).
    
3. Customers use the link to submit a claim through a branded Refund Protect application form.

ℹ️ This link is auto-generated based on order number and user info. No client-side setup is needed for this.

💡 Best Practices & Notes

• Do not reuse vendor codes across multiple sites.
   
• Ensure your staff is aware of where the refund links appear (receipt vs. email).
   
• Customers interact directly with Protect Group for claims — TicketSocket is not involved after purchase.
   

📞 Need Help?

For setup issues or questions:

• Contact your TicketSocket Account Manager.
   
• Or reach out to Protect Group support.