credit-card

When using Stripe in live mode I get this PHP error: No such token tok_fgfhn.. a similar object exists in test mode, but a live mode key was used to make this request Everything works well in Stripe test mode, and and I've switched to a live API key. I create a new customer like this: $token = $_POST['stripeToken']; $email = $_POST['email']; $customer = \Stripe\Customer::create(array( 'email' => $email, 'card' => $token )); //charge for user ads $charge = \Stripe\Charge::create(array( 'customer' => $customer->id, 'amount' => $amount, 'currency' => 'eur' )); I've tested many hours but I still

I want to use Google Play's in-app billing for one of my applications. But it seems I can't use it. First problem is that according to supported locations for merchants my country - Turkey - is not in the list. And as a second problem , my app is listed on some other markets except Google Play. Google Play in-app billing overview section In-app Billing Requirements and Limitations says that In-app billing can be implemented only in applications that you publish through Google Play. Therefore even if Turkey will be in merchant list in the future, I could not use Google Play's in-app billing for

How are purchases of physical products handled in android? Are there any limitants and/or considerations? As I read in this article: http://developer.android.com/guide/market/billing/index.html Android developers are only considering digital products not physical. Nevertheless,I just found an office depot app which let us choose physical products from their store, add them to a shopping car and check them out. Furthermore, when cheking out we also have the chance to add a payment account i.e. credit card, meaning we must use security either for storing credit card data or to send it. When

Should I use sessions for the first few steps (validation, review purchase) then input the information into the database in the final submit? Could the cookies get jacked and transform into a lawsuit? Is it too risky? Would I need to protect my db any special way if storing credit card numbers? Any and all recommendation and personal experiences are welcome. Credit card issues have strict requirements (google "PCI Compliance") about storing credit card data. There's at least one payment gateway that allows you to outsource the compliance stuff: http://www.braintreepaymentsolutions.com/ Last

I am working in PHP on a Linux server with MySQL. I have a requirement (that I have attempted to talk them out of) to collect credit card information from users so that our company can use the card numbers to hold hotel rooms for a conference. We will not be charging the cards ourselves at all, but instead just sending them to the hotel. I then need to be able to download a CSV file and each time someone signs up an email to go to the admin with all the information. I tried to explain that this wasn't secure, but several other developers have done this for them in the past before I was working

I need to do a Credit card number validation. When I googled this I found the org.apache.commons.validator.CreditCardValidator . But seems like it is not working correctly. When I pass a non-digit character also it porvides true. Code for Apache CreditCardValidator : String ccNumber = "378282246310005"; CreditCardValidator creditCardValidator = new CreditCardValidator(); if(!creditCardValidator.isValid(ccNumber)) throw new Exception("Credit Card Number is not a valid one!"); Then, I wrote following methods to validate credit card numbers based on the card type and the card number (using the