Skip to main content

Standard settlements

In a standard settlement, the merchant captures the full amount that was previously authorized. Your system should release the authorization hold and post the transaction for the captured amount. This is the most common settlement flow used in retail environments. When Rain receives the settlement funds from the merchant, Rain sends a transaction.completed webhook with the final amount.

Partial capture

In a partial capture, the merchant settles for less than the authorized amount. After receiving the settlement webhook, your system should release the full authorization hold and post a transaction for the captured amount only. This flow is common in restaurants, where the final charge may be lower than the original authorization after accounting for tips. You will receive a transaction.completed webhook with the final amount.

Over capture

Only available to specific merchant categories:Certain industries are allowed to settle for more than the authorized amount to accommodate tips and similar charges. See the permitted overcapture limits by MCC for specific MCC codes and their permitted overcapture limits.
In an over capture, the merchant settles for more than the originally authorized amount. Rain validates the request against network rules and configured thresholds and may approve or decline it. This flow is typically used in scenarios that involve tips or additional surcharges, such as dining or hospitality. Once Rain receives the settlement funds from the merchant, it sends a transaction.completed webhook with the final amount. To test this in sandbox, use two settlements that sum to a smaller amount. This multiple settlement situation will force it to be completed. To do this, navigate to the Transactions tab and click on the add-settlement-icon (right-most) on the corresponding transaction you want to over capture.

Multi capture

Rain supports multiple partial settlements against a single authorization. The full authorization hold should remain in place until all settlements are completed. Once the final settlement is processed, Rain sends a webhook with the total settled amount. Your system should then release the authorization hold and post the transaction for the total amount. This flow is commonly used in shipping scenarios where items are fulfilled and charged separately against one initial authorization. When Rain receives the settlement funds from the merchant, it sends a transaction.completed webhook with the final amount.

Force capture

Only available to specific merchant categories:In card-absent environments, up to a 15% increase between the authorized and settled amount is typically permitted. This buffer covers adjustments like shipping fees, taxes, or final service charges.
A force capture occurs when a merchant settles a transaction without prior authorization. These transactions bypass the authorization phase and proceed directly to settlement. This flow is typically used in offline scenarios, such as in-flight purchases where the merchant does not have internet access. Once the merchant posts the settlement, you will receive a transaction.completed webhook. These transactions are final.

Refunds

Refunds are treated as negative transactions and may or may not reference the original settlement. Rain validates each refund request based on network rules and merchant configuration before issuing a credit to the cardholder’s account. Unlike reversals, refunds can be initiated independently of the original transaction and may occur well after the initial settlement. Once the settlement is complete, you will receive a transaction.completed webhook. You will then post the refund to your ledger.