I'm currently integrating Squareup APIs for a project. We have a developer account and a merchant account. When I try to test the integration and test payment using Squareup payment form I am getting this error.
{"errors":[{"category":"PAYMENT_METHOD_ERROR","code":"INVALID_CARD","detail":"Invalid card number."}
When I try to use merchant terminal to charge, i'm getting card invalid error page.
Test cards. https://docs.connect.squareup.com/testing/test-values
How can I test credit card processing with test cards?
The way to view sandbox transactions is to call the ListTransactions endpoint with your sandbox credentials to get a sandbox transaction report. Only live transactions will be visible on your Square Dashboard.
To test the full extent of our APIs you'll need to test in production. While there’s not currently a way to delete test transactions, you can definitely process a refund instead. It won’t remove the transactions from your history, but refunding the transaction will balance your books. If you’re not familiar with processing refunds, visit our Support Center for step-by-step instructions.
We're constantly working on adding more features to sandbox. I'll be sure to share your thoughts with the appropriate teams.
Related
I'm using Braintree for my site's payments and it works well except that when a user has selected a payment card from its chrome's history and he/she mistakenly inputs a wrong CVV the Braintree will fail the transaction (when trying to verify) but it saves the credit card and the user cannot edit him/her mistake, and only thing he/she can is to delete the CC using the Braintree's vault manager and re-enter again!
Question:
How can I make drop-in to edit the selected card when the card's verification fails?
Full disclosure: I work at Braintree. If you have any further questions, feel free to contact support.
Vault manager does not allow the ability to edit the CVV (or any values) on the cards saved to the Vault. I can certainly pass this along as a future feature request.
This does not sound like the expected behavior if you are verifying prior to Vaulting in production and have CVV rules enabled to reject if the CVV does not match. If you are running into this error in production, please reach out to our Support team with an example. If this is in sandbox, please ensure you are using a test CVV to trigger the desired response.
I'm developing an application with react native and I am using this library
https://github.com/tipsi/tipsi-stripe in order to use Google Pay with stripe integration.
I already linked the test key from stripe and the merchant Id from play store.
I have a serious issue though. After running the app, when the Google Pay popup form opens,
i get the Google Pay dialog but with a message
"Unrecognized app. Please make sure you trust this app
before proceeding".
However when I enter a test card and press continue I get an additional error that says
Transaction declined: invalid payment method. [OR-CCSEH-05]
I would appreciate any help.
See image below
When testing Google Pay, you actually use real credit cards. That said, I'd be doubly positive you've got your environment set to use Test Mode in Google Pay. Outside of Tipsi, you'd usually set that with the WalletConstants.ENVIRONMENT_TEST constant. Hope that helps!
i've contacted google regarding this case, as i've been facing similar one and upon it's inspection i've received the following reply:
Thanks for being Patient. I apologize for the inconvenience caused.
Upon checking, I understand that you're unable to add testing cards. I would like to inform you that testing cards can't be added to Google Payment profile as payment Method.
Thanks!
upon further investigation by Stripe it self i've been assured:
For a bit of context on how Google Pay works to test payments. When you’re using your test mode API keys, the actual details of the card are ignored, and they get replaced with the Stripe 4242 test card. To test authentication you will not be able to add the test cards to your Google Pay account however there is a work around for this, you add our 3DS test cards to Chrome and use the PaymentRequest button with them (making sure to choose them, and not Google Pay itself). Unfortunately there is no direct method to testing this in your the app.
so setting WalletConstants.ENVIRONMENT_TEST at 5th step of their tutorial should be sufficient and then use your real card.
https://developers.google.com/pay/api/android/guides/tutorial
So, I'm using Paysafe as my payment processor, and they only allow certain card numbers for testing successful transactions. I cannot add these card numbers to my Google account (I get an error that tells me to correct the card number), so it seems that I can't test successful transactions with Google Pay/Paysafe?
When Google Pay is in TEST environment, they say they don't charge cards (even if it's a real card). So would I have to put Paysafe into it's production environment to be able to test a successful transaction with Google Pay, or has anyone gotten around this?
When I send the token from Google Pay to the Paysafe TEST environment, I get this error:
Either the payment token is invalid or the corresponding profile or credit card is not active
But I know I'm getting the right token and sending it properly (since it's a test environment the token is always the same though), so I figure since the Google Pay TEST token card number isn't one of the accepted Paysafe testing card numbers, I'll have to put Paysafe into production and then test Google Pay? Again, if anyone has found a way around this, it would be greatly appreciated.
We are upgrading our SagePay protocol from v2.23 to 3.0 to support surcharge fees. In v3.0 transaction registration post there are CreateToken and StoreToken which was not in the earlier version. What is the reason for create and store tokens? I went through the document but couldn't find a clue.
The link provided in the above post links to advice by one of our Sage Pay Partners so take a look at it.
Token allows shoppers the option of storing their card details (as a token) to their account on the payment page during their first purchase instead of having to set it up manually afterwards. Single click purchases for repeat customers will become much simpler and quicker to set up.
To view the Token Guide go to here, scroll to the bottom of the screen and select the Download the Documents option within your preferred method of integration (server, server inframe, direct). Within the guide it explains creating and storing a token.
If this is a service you would like enabled on your Sage Pay account our New Business team are available 0900-1800 on 0845 111 4466. Prices for Token are available via here. If you have any other questions, our 24/7 Support team can assist to on 0845 111 4455.
Sage Pay Support.
I believe this is related to their token system, allowing you to store and send card details as a token.
If you don't use their token system you don't need to worry about it.
Sage Pay have destroyed their content recently so it's hard to find anything, here's a quick article on their token system - http://www.metakinetic.com/blog/2013/09/sage-pays-token-system-and-advancements-in-payment-gateways/
I was wonder if it's possible to use PayPal mobile checkout directly in my wp7 app, as in-app payment gateway.
My concern it’s Microsoft marketplace application policy 2.1:
“Your application must be fully functional when acquired from Windows
Phone Marketplace (except for additional data as permitted below).
Unless you have a pre-existing billing relationship with the user,
your application may not require the user to provide payment
information,within the application experience, to activate, unlock, or
extend usage of the application. “
Does this means I’m not allowed to use PayPal to make in-app purchasing?
Thank you,
Alex
I think this policy only applies to your app. If you want to use PayPal
to activate, unlock, or extend usage of the application
than it's not allowed. If you want to do other things which require PayPal the policy allows you to do so.
The marketplace requirement menas that you must have that "pre-existing billing relationship with the user". It doesn't put any restriction on how you bill your users. You could, therefore use PayPal or any ither method available to you.
This requirement is partly to enforce the prevention of apps which have no functionality when downloaded from the marketplace, without paying for the content.
I would suggest contacting app hub support to further discuss your specific requirements if you need to or to confirm the exact meaning around what qualifies as a "pre-existing billing relationship".
You can use Paypal. If you study the clause carefully, it states "Unless you have a pre-existing billing relationship with the user, your application may not require the user to provide payment information,within the application experience, to activate, unlock, or extend usage of the application."
f you do not have a pre-existing billing relationship with new users, all they need to do is to complete the payment information outside the app, for example get redirected to an external browser (Paypal) to input their details.
Hope this helps.