Skip to main content
Before and during transaction processing, Rain runs a series of checks to prevent fraud and enforce your controls. This page lists the common decline reasons Rain returns, the authorization codes it uses, the risk rules it enforces by default, and the merchant categories and merchants it blocks.

Decline reasons

Declines can occur for several reasons, including system rules, card limits, and webhook responses. Here is a list of these reasons:
declinedReason isn’t limited to this list: some declines carry the processor’s own description or a risk rule’s description verbatim, so treat unrecognized values as a decline with a free-form reason rather than an error.

Authorization codes

Rain uses specific authorization codes to classify the context and status of each transaction. Here are some commonly encountered codes:

Risk rules

Rain enforces automatic risk detection rules to prevent high-risk or suspicious transactions. Each rule includes a time window and trigger threshold:

Blocked merchant categories and merchants

Rain blocks certain merchant category codes and specific merchants by default. The canonical lists live on Blocked MCCs and merchants; this page doesn’t duplicate them so they can’t drift apart.

What’s next

3-D Secure

Forward 3-D Secure challenges to cardholders for online transactions.

Blocked MCCs and merchants

Review the merchant categories and merchants Rain blocks by default.

Handle disputes and refunds

File disputes, track their status, and process refunds.