Authorize.net AVS error page handling - error-handling

I am simulating an AVS error and the response displayed -
An error occurred while trying to report this transaction to the merchant.
An e-mail has been sent to the merchant informing them of the error.
The following is the result of the attempt to charge your credit card.
The transaction has been declined because of an AVS mismatch.
The address provided does not match billing address of cardholder.
There is nothing else on the screen, the url is pointing to https://test.authorize.net/gateway/transact.dll
I hate to give this option to the client without some type of instruction like a back button. Other simulated errors usually stay on the form page.

This error occurs when Authorize.Net is trying to contact your website's relay response page and it does not respond successfully withing a specified period of time. Authorize.Net offers more detail on their website.

Related

ApplePay JS fails before onpaymentauthorized

I'm trying to set up Apple Pay on our website and having trouble getting the "onpaymentauthorized" to fire. Everything is working up to that point, the sheet comes down and the other handlers fire and respond as expected. However once authenticate the final payment the sheet displays "Payment Not Completed" and asks for for my password again.
I've seen a lot of people see a similar error on the merchant validation when the url of the requestURI doesn't match the url submitted for validation but I already dealt with that issue.
is there any way I could see more information on why Apple Pay might be failing?

BlueSnap Subscription Fail simulation

Is there any way to simulate bluesnap. what happens when a recurring payment fails, for example, if the user doesn't have money on the card in that moment?
Thank in advance :)
BlueSnap offers IPN (Instant Payment Notification) alerts for events such as declined CC charge for a subscription. This type of IPN is defined as "on demand" - which means you will need to register to receive it in the BlueSnap control panel.
https://support.bluesnap.com/docs/on-demand-ipns
Since the IPNs are messages sent over HTTP, you can choose to send them to your server, and configure a receiver for it there. Once the IPN reached your server it can be parsed by your receiver and you can choose what to do with it, for example:
send an automated email to your customer support or accounting department
send an email to the shopper
log the event in your system for later analysis.
IPNs can also be sent manually, thus simulating this event. For you specific case, the IPN for CC_CHARGE_FAILED can by opening a browser with a connection that can access your server, and putting the IPN in the address line. Your receiver will get the information and respond accordingly.
If you already received an IPN for an actual CC charge failure - use that IPN message as is. If you have not yet received such an IPN and in fact you're just starting out and building your own receiver, you should contact BlueSnap merchant support at merchants#bluesnap.com and they'll send you a sample.

ERROR : 401 loginpost URL timed out,

While linking one of our bank account from HDFC bank india we see an error message stating :
ERROR : 401 : HDFC Bank (India) - Bank and Credit Card
As part of our internal proactive monitoring initiative, we have observed that agent is failing with 401 because loginpost URL timed out.
Let me know does these banks are not supported within yodlee or is there any access restriction.
Besides this API accepts invalid login too and returns has site(bank name) added successfully.
Let me know how to solve these problems
Thanks In Advance.
This error comes when Yodlee is not able to connect with the Bank website in a defined time frame. This could happen due to various reasons,one of basic reason is that Site is taking too much time to load or open login page.
For your reference here is the details about different error codes.
On your second question: Where you have mentioned that this API takes invalid login credentials as well.
To explain you the process- You'll provide the credentials(whether correct or incorrect) to this API, then Yodlee uses those credentials and try to login at the bank website while if site says that the credentials are invalid Yodlee returns the respective error code and message. Hope this helps.

Paypal ipn processing and dropdown option/price buttons logic

I read lots of post from various sites including paypal documentations. But I have some quesitons wihch I couldnt solve those. One of them is that how to design the codes after receiving the ipn message. Ofcourse I make my code I am able to optain and process the variables of message. like payment status and I am able to save them into database. But the point is that how should I desing the code to control the payment to overcome my requirements. I know the post become long but I feel the need of this explanation. So I have a site which works with membership with payment. Site is check after login the membership trial is expired or not if it is expired it shows a div in fornt of the site wihch includes the paypal buttons and redirect to paypal payment screen when button is clicked. User shodul have ability to choos membership period like 6 or 12 mounths (by dropdown paypal button). When the user finalize his payment ipn is trrigerd and I get the datas but all my members dont have to have a paypal account so they can use therid credit card directli and if I understand correctly the transfer of money can take some time to be recevied by me. Which time interval I should set the members approved flag is true ? I am confused about this. If I approve him after ipn is sent is there a possibility an error can occure while transferring me. How the process works.
other problem is the dropdown button. when I set option/price button when I click the button an error page is shown after redirecting to my selling page. It does not redirect to the payment page.
Realy sorry for my long post but I dont know how can I descirebethe situtation in a short way
If you need to wait until funds are available, you should test the value of "payment_status" in the verified IPN message for "Completed".
An eCheck can take from 3-5 days for collection (sometimes longer; you can see the estimated hold time in your account) and has payment_status="Pending". Once collected, you will get another IPN message with "Completed".
Note that the user never sees the IPN process. Normally you set up the conditions (in a table or something that is persistent enough), then send the user to PayPal. When the user comes back from PayPal, your code (at the "return_url") checks the table to see if Payment had completed successfully (perhaps a flag, which was set by your IPN handler code that is called by/communicated with PayPal when the user leaves PayPal gracefully).

Test Magento 1.6.2.0 Direct Post Authorize.net payment method with test credit cards

Has anyone tried testing the Authorize.net Direct Post Method with test credit cards using Magento 1.6.2.0?
I tried using the 4111111111111111 Visa test credit cards, switching the Authorize.net account from test mode:on and test mode:off.These transactions are captured on Authorize.net account but the checkout page in Magento does not redirect to Success page, instead i get an error message
An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card. This transaction has been approved. It is advisable for you to contact the merchant to verify that you will receive the product or service.
Could someone elaborate on how to test credit card transactions in Magento 1.6.2.0 using Direct Post Authorize.net payment method?
The Direct Post Method requires Authorize.net open a communication to your server (essentially, the customer sends information directly to Authorize.Net including the credit card number, expiration date, etc... as well as a URL that Authorize.Net uses to communicate to your server). Because of this, your test site will need to be publicly accessible (i.e. firewall open, with a domain name registered and pointed to the site).