PayPal Risk Model Error 10626

Presented with the Short Message Risk, the Long Message Transaction Refused Due To Risk Model, and the Error Code 10626 from the PayPal payment gateway, a regular customer is getting confused moving to irritated that we are unable to take a payment. Their bank says all is good. Yet we keep rejecting them. The error message specifically reads:

 L_ERRORCODE0 => 10626
 L_LONGMESSAGE0 => Transaction refused due to risk model

Well that *is* crystal clear.

Furthermore "the bank confirm they did not reject the payment" - and then magically later the payment goes through when retried.

There do not appear to be any firm answers out there, and PayPal do not appear to be interested (shocker). So this begs the question - what is going on here?

"Contact the buyer." is something further on this error code when you look over the API documentation - but nothing specific as to what is causing this. In full we have:

So lets drop back to Developer Documentation for the PayPal API - and see what sunshine it has to share there then:

 Error Code: 10626
 Short Message: Risk
 Long Message: Transaction refused due to risk model.
 Returned by API Call: DoAuthorization, DoCapture, DoVoid.
 Correcting this error: Contact the buyer.



Best guess - that this is similar to the kinds of mechanisms we would employ for where an email account is being used for. Jakarta, Mozambique, and Chester... at once, possibly going to be something going on for right? Right. This is probably the same well meaning AI that gets you a call when you buy the same thing you do every day, at the same time, for the same amount, and suddenly they are checking you are you and making that transaction. The same kinds of AI that thinks that item you searched for on Amazon was for you, and you REALLY NEED that My Little Pony - still, despite looking up a price, once, ever. Meta-data - what a beautiful and indicative pool of identity you are.

On the upside - credit is one of the largest uses of supercomputing power - or at least used to be, after nuclear arsenal decay, and weather computational tasks. Yet again a proof for "enough monkeys with type writers".

However - as faulty as well meaning may code my present - wouldn't it be good if the DOCUMENTATION ACTUALLY SAID THAT - rather than feeling the need to post a best guess to cut short he search of others.

Seriously. Have a word with yourselves, make that something we can answer, help the vendor hate you less.

3 Responses to “PayPal Risk Model Error 10626

  • Ever get any clarity on what was causing this? We’re getting hit by the same thing.

  • anthony
    8 years ago

    No. In a word.

    However the assumption that I made above fits well.

    They are reasonably autonomous, and are not really that interested in interactions that are not revenue generating.

    I no longer try submit caches of likely compromised account details from p0wn3d hosting accounts, they really don’t seem interested in anything that isn’t compliance, liability, and income… at which point they are right back to you.

    As such the chance of getting a straight answer back on this is equally low to none. However, if you, or indeed someone else should happen to have a definitive answer – DO SHARE.

  • anthony
    8 years ago

    Follow up on this again – after a colleague exclaimed that he must be onto a loser as he was looking for something and found something that I had written… more strength indeed to the location model of answer. If the IP of the requester is being passed this may be the issue.

    In our case we are using this with WHMCS – as you would as a hosting provider.

    In this particular case the account was setup with an IP in Cuba. Simply changing the requesting IP (to our own, as we were placing the payment now) – and the request went through, after it failing from their location.

    This does not detract from the fact that this is an appallingly handled error message. Vague in error message, and vague in documentation.

Leave a Reply

Your email address will not be published. Required fields are marked *