in google payment method for subscribing new google developer account when we proceed continue to payment and enters all required information about Visa Card correctly, and click ay buy button, it process and at the end gives message for
card declined
while giving following error
An unexpected error occurred. Please try again later. (686578003)
where as I've confirmed about card number while removing and resubmitting it. I've also cleared browsing data including cache and cookies. nothing works on my side.
Could anyone explain what it means with following error code
686578003
in google while purchasing developer account or developer console?
Related
I first tried to create a new google play console account. At that time, I didn't have enough balance on my card and payment was unsuccessful. However, Google sent me an email to retry making the payment immediately but I didn't try that again since I didn't have sufficient balance on my card.
A few days later, I got some balance on my card and I made the payment via the link that Google sent to me after the unsuccessful payment. Then, payment was successful. The issue is that I could not get access to the Google Play Console after this. When I visited the website, it asks me to register a new account.
I tried to contact Google Support but didn't find a way to do it. I waited 4 days til now despite not receiving any updates from them.
Could you guys please let me know what the process is and how long it usually takes? Or do I have to create a new account and lose the money I paid for the previous one?
I am trying to use a custom domain for a node.js app I'm hosting on heroku.
For that I am trying to use my card to verify my account, however I keep getting a general error message or I get "Error Unable to verify your card. Please try later or contact your financial institution for help."
I checked with my bank and they said the bank and Visa are allowing the transaction to go through. The charges even show as pending on my bank statement.
So I'm not sure what is preventing my account from getting verified.
Any suggestions would be helpful
I am using omnipay package for my payment method in authorized.
I have two site on the same server, one is a live site that runs ssl and one that is for testing purposes only and do not run ssl.
Now, i dont have problem on paying in our testing site which it runs within our expectation. But, it seems odd in our live site because after entering my billing information, it returns an error that says:
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.
Where do u think the problem lies? I really need help on this. Thanks!
This means the relay response URL used by your application is not returning a successful response to Authorize.Net in time (5 seconds). As a result Authorize.Net is assuming the page is not functioning and displaying that message.
You either need to verify the URL is correct, not error-ing out, and responding within a few seconds.
I'm having the most trouble with Paypal. We already have a system set up that is working our live site, but I created a test-only Payflow account for testing configured exactly how we have it in live, but it keeps timing out or giving me the error
"Information entered incorrect. Try again.". The code has not changed.
Just yesterday before I left for the day it was working for once. I don't know what I'm doing wrong.
Posting to this URL: https://pilot-payflowlink.paypal.com/
Login = My Login
Partner = PayPal
Amount = 5
Type = S
I have turned everything as "OPTIONAL" as far as address and billing goes. All that displays is the credit card number and expiration, but after it gives me the "Information entered incorrect. Try again." it displays a radio button that asks if the address is the same as the shipping. if I click different it does nothing, I think it should at least drop down with some other fields.
Payflow manager:
In Payflow manager if i try a test transaction under Virtual Terminal > Test Single Transaction it gives me this error:
Tender Type: Credit Card
Transaction: Sale
Card Number: 371449635398431
Mode: Test
I give it $5, nothing else filled in:
Result Code: 104 Response Message: Timeout waiting for Processor
response
It's a project I need to finish as quickly as possible but looks like Paypal isn't letting this happen. Also, I am using the test credit card numbers found in the docs.
Test link: http://cityoftemplates.com/email_process_test/tests/clientCheckout/
The gateway with no changes to what I had done earlier started working.
I assume it was some kind of maintenance or downtime caused by POODLE (SSLv4 bug) that made it go down all morning.
I have set up payment processing through Authorize.net (actually through a reseller) and I am able to successfully perform Test transactions. However, when I perform real transactions, I get a Rejected transaction. When I check the transaction in the authorize.net account I see "General Error (Request rejected by FDC Omaha - Wrong Merchant Type). I assume this is some sort of configuration problem between First Data and authorize.net or me. However, I have no way of telling exactly what the problem is. Authorize.net told me to contact my MSP and the reseller is saying there is nothing they can do to fix the problem (I find it hard to believe.) Is this a setting on my side that I can fix? Help!
You must contact your merchant account provider to fix this error. I've seen this error message several times with our customers at www.authnetscripts.com.
The error indicates a mis-configuration with the processor.
Thanks!
We got this error recently on one of our sites, so we followed the advice to call the merchant account provider.
We called and they told us that sometimes you can get this error because of the type of card (MasterCard, Visa, Discover, AmEx, etc.) that is being used. We tried a different type of card and it processed correctly.
Hopefully that helps someone else who runs into this same problem.