Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I was wondering what is the best practice to refund a charge that was only made for verification. Lets assume a customer updates his/her card while having an active subscription. To make sure a charge can be made to that new card, I create a small charge of 50 cent.
Of course, the customer will get these 50 cents back. Right now, I start the refund about a second after I made that charge.
I was wondering if that is the best practice. I know a bunch of companies do that, but the refund usually appears about 1-5 days later, not right after making the payment. Is this common, or should I use a cronjob to refund a day later or so? I was just wondering if there is any potential downside of refunding right away.
You should not be making these charges at all, so best practices about refunding them are moot.
Instead, you should use Setup Intents to collect card details for later payments, including 3D Secure authentication if required.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
It's a common feature for payment providers to have a medium to store card details(which returns a reference you can always use to charge a card).
We plan on leveraging multiple payment providers, considering that our product is used by various regions (both to support the locally available cards and alongside maintain low payment charges incurred by the customer, based on their location).
Now the challenge is that each time we integrate a new payment provider, it'll require that we replicate/store all of our existing users' card details (already stored on other payment providers we leverage on) on the new provider we'll be integrating with.
Knowing fully well that:
We don't store users' card
Previously integrated payment providers don't return complete card details (just reference).
Payment providers cannot allow transferring card details to another provider.
I'm hereby seeking an alternative solution (that doesn't require storing card).
I saw something close to what we could rely on(https://www.spreedly.com/). Are there also alternatives to this?
If you want to do this, your only options are to use a vaulting product like Spreedly or become PCI certified yourself - and using a vaulting product is going to be a lot easier to deal with than the PCI certification you'll need to store the cards yourself.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'd love to know if there is a steam API or something, that gets all current steam games and their price? I need to make a Steam Key Trading Bot that sells Steam Game Keys so I need prices of games and actual games to update automatically.
So what I'm asking is if anyone knows where I can get my hands on an automatic updating Steam Games and Pricelist.
I know this exists:
http://api.steampowered.com/ISteamApps/GetAppList/v0001
But it dosen't include price..
You can get detailed information about apps by making a request to
http://store.steampowered.com/api/appdetails?appids=<appid>
The JSON response contains a field called price_overview which holds the price- and discount-information.
However, you have to make this request for each app you want to check.
EDIT:
According to this post, the support for multiple appids has been removed and the api is limited to 200 requests per 5 minutes.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
People buy stuff on my site through PayPal or payment card. I need to refund some clients now but I don't have their payment/card/bank details that I could use to do so.
Considering that not storing payment details is common and refunding people is also common, what is the usual solution to deal with this situation?
Presumably you have the original order details stored, so you'll have their name, transaction reference, payment method, etc. For PayPal payments, you can issue a refund directly from your PayPal account - just cross reference the order details you have with those stored in PayPal.
For other card payments, what payment processor do you use? All the main processors have refund functionality built into their APIs. In my experience, the payment processor (who is PCI compliant) stores the card details and provides you with a unique token that identifies that card. You then communicate with them using that token, so any payments or refunds can be processed on the right card.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm launching a startup web site, what i would like to know is how to start with that, i mean is better to use invitations first of all?
Then how to send invitations and to who?
How can i plan invitations? Which are best practices?
Does anyone is passed from this step with his own site?
Any experience on here?
thanks
Whether you create a beta version of the site first is completely up to you.
It really depends what type of website you're planning to make. Beta's are obviously a good way to gain feedback on your website and its functionality before releasing to everyone. Thus, allowing you to make improvements/fix bugs before everyone uses the site.
In terms of actually getting users for the beta, it's very much a case of marketing your website and its existence well (through social media, advertising etc.), and then providing some kind of 'sign up for the beta' page. You could then close registration for the beta once you have enough users, and devise some method of gaining feedback from users.
I haven't personally created a beta myself, but if I was to do it, I would do the above.
Hope that's of some help.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Let's say I am selling some PHP scripts, developed from scratch by me, and also some Flash games, also developed from scratch by me.
I sold the flash games and PHP scripts to some clients, and to some of them I even sold them with source codes.
Now if one customer will sell the code to someone else without my approval, and that someone else, the 3rd person would claim that the code belongs to him, what can be done?
Can PHP scripts or codes be signed online or something like that?
When you sold to clients, does the contract stipulate that they are forbidden to sell it ? Also more importantly does the contract also specify that the client must not modify in anyway the source code and then sell it ?
Today, the best way to protect your I.P. is to use a lawyer and yes, this is a sad thing.
You're trying to solve a social problem by technological means. This won't work.
If someone does that to you, you should get a lawyer and sue him.