I have integrated react PayPal button to in my react app using live client id but when I am trying to make payment using my PayPal account it is showing error We’re sorry. This seller doesn’t accept payments in your currency. Please return to the seller and choose another way to pay..
Searched a lot in google but did not found any helpful source.
Please if you have clue about this kindly help me, struggling for the last 3 days.
Thanks in advance for you any help.
For instance AFAIK there is one possible reason for such an error:
for some countries (e.g. Russian Federation) there is an internal
law avoiding payments in other currency rather than russian rouble
between russian residents.
in this case if payer and payee are both russian residents , payment
won't work if price for product or service is set in USD/EUR .
Looks like India and Russia have similar restrictions regarding to domestic payment currencies. There are some recommendations for India which are useful for Russia as well.
To test that your integration works correctly in case of an international buyer, you may want to create one more sandbox personal PayPal account (with US country of origin). Then you'll be able to invoice and accept payments from both Russian buyer (in rubles) and US buyer (in USD).
Related
I am integrating PayPal checkout with react using SDK. The seller currency is USD. I am testing it with an Indian sandbox account. The transaction is successful with all other accounts except for Indian Accounts. In all other cases, the sandbox does the currency conversion and pays the amount accordingly except in Indian currency which says the seller doesn't accept payment in your currency. What might be the possible issue? Any suggestions would be highly appreciated.
The issue is explained here in footnote (3) for INR.
"This currency is supported as a payment currency and a currency
balance for in-country PayPal India accounts only."
The problem was with sandbox account created. This account was created to accept payment in an only particular currency. The problem got resolved by using other sandbox business account which accepts payment in all currencies.
I have a website(PHP) which has payment functionality with recuring/autopayment feature where user will enter their credit card detail once for shopping and from next time onward they don't need to enter their credit card detail again. Credit Card detail will not be saved to my database but will be saved in payment gateway with unique id/reference. I just need to use reference id for payment whenever user do shpping.
Earlier, i was using authorize.net payment gateway with its CIM(Customer Information Management) feature for auto payment which was working fine but now my client does want this payment gateway. I want some alternate payment gateway which support CIM feature.
If someone has already done same kind of stuff then please help me.
Authorized.net is the best option, because of reputation, costs and developer friendly environment. However there are alternatives as stripe, 2checkout, braintree...
I intend to develop a client for Amazon's Marketplace webservices (MWS). My requirements would be to update the order, synchronize the order status, get the order details using the APIs they have.
However, I could not find a Sandbox environment to test these scenarios. Amazon has a payment Sandbox I understand, but is there a sandbox available to test these web-services? If not, are there any pointers on how to go about testing the above mentioned scenarios with Amazon MWS?
UPDATE
As seen in the comments to this post, Amazon no longer provides a staging / test environment.
I just had a conversation via sellercentral ticket with an amazon employee.
They said:
We can provide you with a free Seller Central test account to be used in ungated categories only, which are the Amazon categories that do not require approval to sell in. For a list of ungated categories, please scroll down to the middle of the page here: http://www.amazonservices.com/content/sell-on-amazon.htm.
For orders:
After you’ve logged into the staging site, you then need to log into a real Amazon buyer account (not your staging account) to buy items. Then, navigate to the offers you’ve created. If you want to buy anything from your staging account (in order to test MWS order functionality) you will be using real credit card data, so make sure your offers are priced at only one cent, and your shipping is also set to one cent. These offers will not be visible on Amazon .com. Do not buy from any other sellers on the staging site.
So (conclusion): Just file a ticket** and tell them you want a seller central test account like this!
First register** for an account that you can access seller central with (please note, that some kind of accounts have a monthly fee, so choose a "per sale" plan. This fee won't be charged with your test account), then you can file the ticket (click the link above).
All resources about the MWS API are here.
** Replace ".com" with your local Domain for the Amazon Site you want a test (staging) account for.
You can use the scratchpad of Amazon:
scratchpad
good luck
I have a website and I would like to implement a paid subscription service. Its a simple service with only 2 types of plans. For now, ill just use Paypal. But im a little lost before start, mainly with the data model.
My main question for now is, what information do I need to keep for each subscription? Do I need to implement a shopping cart for this (dont think so)? Im not asking for a detailed explanation, just a few lights or resources to find a way to start. Thanks.
Depends on what technology you're using. Basic payments work a bit like this
-> You send them to paypal with a plan (you define the plan on paypal)
they know which amount to charge
you can pass custom parameters which they will pass back
Customer fills in application
<- paypal tells you that your predefined plan got purchased
in this same request, they send a lot of info about the payment including a GUID and your params
-> you ask paypal "hey, some one just told me this plan GUID got purchased, can you confirm"
<- paypal service returns 'yes'
-> you take the customer's ID from the params that you attached when you sent them to the paypal service and update them to "paid" in the database, or whatever
That's it in a nutshell...
Look at any subscription card mailer from any magazine and you can get an idea of what kind of data you will have to record. Start and end date for the subscription would be a good thing to keep, and what kind of plan the user is subscribed to. Once you have the end date, you just need to run a query to get the records of the users that have access. Something like
Select * from users where subscription_end_date is >= today
I'm sure there will be a lot of other columns that will go into your final product, but that will be up to you to decide what data you want to keep. What are the different states that a subscription can be in? Can someone be subscribed to both services at the same time?
PayPal does a decent job if you want to charge the same amount every month. However, if you anticipate your users making changes to their subscription plans (upgrades/downgrades) or needing to provide credits to their account for customer support purposes, PayPal would require that you cancel the subscription...and then have the customer re-subscribe.
[Full disclosure - I am a co-founder of Recurly.com]
Recurly handles the upgrades and downgrades, and provides automated customer emails to be sent out to your customers (on your behalf) for every event confirmation, and invoice that occurs. You also have a full account management dashboard and reporting so that you don't need to build this yourself.
Best of all, if you ever decide to leave PayPal, and move your business to a standalone payment gateway, Recurly stores all of your credit cards in a PCI compliant vault so you don't need to ask you customers to come back and re-subscribe. (PayPal will not return your customer credit card information). You simply configure your new gateway in Recurly, and payments will be processed without any interruption to your business.
Here is a blog post we wrote on the topic:
http://blog.recurly.com/2010/08/top-ten-reasons-to-use-recurly-vs-paypal-for-recurring-billing/
-Best of luck.
-Dan
i am developing an affiliate site.
it uses linkshare and commission junction.
it is for our client. so i do not have any account with any network or agent. either with popshops or the networks.
the client has registered with popshops to display merchants.
when users click links we need to know which user had purchased which product by sending some information to affiliate networks using the sid option.
every thing fine except a sandbox.
how do we do a test drive with link share and commission junction?
else we have to wait till an user purchases a product.
any suggestion and comments would be helpful.
They don't offer a sandbox, you will need to just know what the API results will be.
It is pretty well documented, but that's all they offer.
If you want, I recommend buying something from one of your affiliates and use that piece of info for testing. Most affiliates don't mind, and I have never found anything in a contract that mentions the affiliate using their own link.