Finix supports full and partial refunds after a payment has been processed. Multiple partial refunds may be made against a payment, but their combined amount cannot exceed the original transaction amount. A refund is a return of customer payment, not a merchant payout or an additional charge. Source: Finix Refunds.
Before acting, identify the original transaction, confirm the amount already refunded, and establish the approved amount still to return.
Verify the commercial decision first
A customer’s request needs to be matched to the correct order and payment.
Check whether the requested amount covers the full order, one item, a canceled portion of a service, or another agreed adjustment. Record who approved the decision and why.
An amount remaining in the order system may differ from the original payment if there have been earlier refunds or additional purchases. Resolve that difference before submitting another refund.
Use a transaction reference wherever possible. Similar names or identical payment amounts are not enough to establish that the correct record has been selected.
The documented Dashboard route
Finix’s Dashboard guide describes this process:
- Expand Transactions and select Payments.
- Open the payment and choose View All Details.
- Find the Refunds section and select Issue Refund.
- Enter or confirm the amount.
- Choose Refund and confirm the total.
The guide describes an initial pending state followed by a succeeded state when processing completes. Use the actual result, rather than the act of clicking the button, to determine what happened. Source: Refunding with the Dashboard.
If the controls are unavailable, use the appropriate account administrator or provider support route. Do not infer that every Dashboard user has the same permissions.
Calculate a partial refund from the payment history
Suppose a fictitious customer paid $300 and has already received a $75 refund. The remaining amount available within that original payment is $225.
If the business approves another $50 refund, the cumulative amount becomes $125, leaving $175 of the original payment unrefunded.
This example illustrates the documented limit. It does not establish how much the customer is entitled to under the sale agreement.
Keep the commercial decision and the payment history together so another staff member does not issue the same adjustment twice.
Understand pending and customer-visible timing
Finix describes a pending-refund workflow when refund holds apply and funding needs to cover the request. It says customers typically see a refund within five to ten business days, depending on their bank. It also states that an initiated refund cannot be canceled. Source: Finix refund processing and timing.
Tell the customer what is known: the refund was requested, it is pending, or the provider reports processing success. Do not promise that the customer’s bank has posted the credit unless that is actually established.
If the request remains unresolved, investigate its status before initiating another monetary action.
Account for the merchant-side cost
Returning the purchase amount does not necessarily reverse the merchant’s original processing expense. Finix states that original processing and platform fees are not returned, and that an additional fixed refund-attempt fee depends on the Fee Profile. Source: Finix refund fees.
Track the customer refund and the related business expense separately. The pricing guide explains how exception activity can affect overall cost.
Check for another active process
Before refunding a transaction associated with an open dispute, review the case through the appropriate provider process. Do not assume that issuing a separate refund automatically resolves the dispute.
For an ACH payment, consult the ACH guide before an early refund. The underlying debit may still be progressing or subject to return.
Finally, update the order record and retain the refund reference. The reconciliation guide shows how to connect that event to later settlement activity.