NewNo plan feeNo plan fee. Just 2.9% + $0.30 per card sale, and signing up is free.Try now →

Checkout.com · Decline codes

What does Checkout.com 41101 “Risk Blocked Transaction” mean?

Checked

Checkout.com 41101 "Risk Blocked Transaction" means the payment was declined by a client-level risk rule, one of the rules you set in Checkout.com's Fraud Detection. The bank never saw it. If a good customer was blocked, the fix is adjusting the rule, not asking them to retry.

Type
Risk response (4xxxx)
Who declined
Your own Checkout.com risk rules (client level)
Retry
Not until the rule changes
Shopper action
Try another method or contact the store
Merchant action
Review which of your rules fired

What PlatformDTC does

In PlatformDTC's routing table 41101 from Checkout.com is a fraud stop: checkout offers no backup processor and no automatic retry, so a blocked payment cannot slip through another route. A subscription renewal declined with 41101 is never retried: the subscription is held past due and the customer is emailed a link to add a new card.

Why it happens

A rule in your client-level risk strategy matched this payment and its action was to decline.

What the shopper can do

Contact the store or use another payment method.

What the store can do

Open the payment's fraud assessment in the Dashboard to see the rule, then tune it if it is catching genuine buyers.

For developers

The payment carries response_code 41101 with a response_summary such as "Risk Blocked Transaction". For 4xxxx codes Checkout.com says the response_code and status depend on the action set in your Fraud Detection risk strategies, so check the payment's fraud assessment in the Dashboard (Payments > Processing > All payments, then the Payment timeline).

Frequently asked questions

Did the bank decline Checkout.com 41101?
No. Your own client-level risk rule did.
What is client level?
Checkout.com separates client-level, entity-level and Checkout.com-level risk responses; 41xxx codes are client level.

Sources

Related

Payments library