Handling Refund Synchronization Issues with Flywire in Dryfta

How does Dryfta handle refund transmissions to Flywire, and what should admins do if participants do not receive refunds after Dryfta shows the order as refunded? Also, how to address duplicate refund entries appearing in Dryfta's audit logs?

Dryfta updates the status of tickets and orders to 'refunded' internally for reporting and tracking purposes but does not initiate the actual refund transaction to payment processors like Flywire. To complete a refund, event admins must log in directly to the Flywire dashboard and process the refund there according to the refund amount decided based on their cancellation policy. 

Automated refund is currently available when using Stripe and Mollie.

If a participant reports that they have not received a refund despite Dryfta showing the order as refunded, admins should verify and issue the refund via Flywire directly, as Dryfta does not transmit refund instructions automatically.

Regarding duplicate refund entries in Dryfta's audit logs, these typically reflect refund actions recorded in the system and may correspond to separate refund processes initiated by the admin. Since Dryfta only records these internally and does not consolidate or transmit refund amounts to Flywire, admins should ensure only the correct refund amount is processed through Flywire. If an incorrect amount was recorded or multiple refund entries exist, admins need to manage adjustments by issuing the correct refund via Flywire and contacting Flywire support if reversal or correction is needed on their side.

In summary, refund processing involves separate steps: updating Dryfta's records for internal management and processing the actual funds transfer directly on the payment platform's dashboard. Close coordination between these systems and careful admin action are required to avoid discrepancies or participant disputes.