Top 3 Error Sources for failed transactions

In this article we want to explain briefly the top 3 error sources for failed transactions in the RaiseNow Manager and how you can detect them. 

1. Bad credit card entries (Final Error) 

While entering information into our Lema widget a first validation of credit card details already occurs. For example, the Lema checks whether the CVV number is three digits or that the credit card number only contains of digits.
If this first validation fails the donor will not be able to submit the donations by clicking on "Securely transmit donations".

The validation of the correctness of the numbers and data is being done by the bank after transmitting the donation. If something is wrong with the credit card details the donor will see an error message on screen indicating that something went wrong with the payment and the contact details of your organization. 

In the RaiseNow Manager you can then check as following what the exact issue with the transaction was. 

Wrong CVV number:

Credit card expired: 

3D Secure error:

2. Limit reached / Card blocked (Final Error) 

For a higher donation an error could occur when the donor or the bank has set a maximum transaction volume to the credit card. If this is the case, the error message in the manager will be 'Limit exceeded' and the donor needs to get in touch with his bank. 

It is possible that the card is completely blocked for online payments. This will also result in a failed transaction and the error message will be 'card blocked'.

Read more about Datatrans error codes here: https://docs.datatrans.ch/docs/api-response-codes

3. SMS Timeout (Final Error) (only in Switzerland) 

For an SMS donation of more than 10 CHF or for a SMS donation via a donation form, a donor must confirm the donation on request with 'YES' within one hour.
If the donor misses this time window or does not confirm the donation at all, the donation will not go through and the transaction will be set to 'Final Error' in the manager. When this happens, you can see it in the manager by the error message 'optintimeout'.