When a ticket purchase is refunded in Funraisin, MoveData cannot automatically match the refund to the original Opportunity record in Salesforce. This article explains why and describes the impact on your Salesforce data.

How it works#

Funraisin handles ticket purchases and ticket refunds differently at the API level:

• Ticket purchases are categorised as a "raffle" object in the Funraisin API. MoveData processes these and creates Opportunity records in Salesforce.
• Ticket refunds are categorised as a "donation" object in the Funraisin API, with no reference to the original ticket purchase transaction.

Because the refund arrives as a different object type with no link to the original transaction, MoveData cannot match the refund to the correct Opportunity record in Salesforce.

What happens when a ticket is refunded#

When Funraisin sends a ticket refund notification to MoveData:

1. MoveData receives the refund as a "donation" type notification.
2. MoveData attempts to process it, but cannot find the original ticket transaction to match against.
3. The notification fails with a processing error.

How to handle ticket refunds#

Because MoveData cannot process ticket refunds automatically, you will need to handle them manually:

1. When a ticket refund notification fails in MoveData, note the refund details from the notification.
2. In Salesforce, find the original Opportunity record for the ticket purchase.
3. Update the Opportunity to reflect the refund (for example, change the Stage to "Refunded" or adjust the Amount).

Related articles#

• Setting up Funraisin
• How Commerce and Tickets Are Processed
• Reading and Understanding Error Messages
• How to Reprocess Failed Notifications