900140 - Unable to purchase application with Credit Card - "Sorry, there was a problem. Please try again later" (Seahorse)

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

Description

[rodrigo.karuki]

Attachment: ezboot-http_07312013-UnableToPurchase.log

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212

Steps to reproduce:

1. Start MarketPlace
2. Search for a paid app
3. Click to purchase
4. Enter PIN
5. Enter correct credit card information



Actual results:

The following message is displayed and the payment is cancelled: Sorry, there was a problem. Please try again later"


Expected results:

Application should be purchased without problem

Comment 1

[rodrigo.karuki]

Attachment: 2013-07-31-14-31-47-SorryUnabletoPurchase.png

Comment 2

[Kumar McMillan [:kumar]]

this is a Bango screen

Comment 3

[karina.filipe]

Attachment: Log with purchase success

Comment 4

[karina.filipe]

Attachment: Failed updated (Aug2nd) log

Comment 5

[karina.filipe]

The system is pretty unstable today.
At the same time, Rodrigo and I tried purchases and in my device I could make purchases, but he couldn't do in his device and the spare one we have.
I could successfully finish my test purchasing every app tier, but after a few hours, as Rodrigo borrowed my device, it stop working.
First, we saw a message informing that there is not enough funds to pay for the app (and the credit card is fine) and then the "sorry, please try again later" message started to be displayed.
We were both using two international (Brazil) credit cards with enough limit and we're switching both credit card numbers. I could purchase with both CC numbers.
Credit cards ending:
5843
4844

Comment 6

[Tom]

No errors occuring on 4844.

Card 5843 had 2 declines due to potential fraud from Card issuer.

Comment 7

[Steve Ruston]

Karina, is this now working? If you need I have a USD credit card which may work

Comment 8

[karina.filipe]

Hi Steve,

I just tried today and none of my cards worked.
Is 5843 having problems? I tried to call the bank, but everytime I try it, I get a message that I cannot make the call from Venezuela, so if there is something wrong with this card (I hope is not) I cannot fix it.

Last friday I was able to purchase all of the applications, while Rodrigo (trying with the very same cards, but alternating them, so the bank would not block for duplicated purchase) could not buy any app.

We have 3 samples of the device, and marked the one that succeeded on Friday. Today, all of the samples are not able to purchase anything yet.

Comment 9

[rodrigo.karuki]

Attachment: bango-whoami-phone1.png

Comment 10

[rodrigo.karuki]

Attachment: bango-whoami-phone2.png

Comment 11

[rodrigo.karuki]

Attachment: bango-whoami-phone3.png

Comment 12

[rodrigo.karuki]

Just included the who am i screenshots.
Since the phone numbers were not displayed (all of the devices contained SIM cards during the test), here are the numbers:

00584142088757
00584149182309
00584142075123

Comment 13

[Keir Kettle]

Background - for end users the Bango credit card system doesn't allow credit card purchases with cards registered in another country, and if you get multiple declines the system will stop offering credit card as an payment option (to prevent fraud) by 'barring' the user.

You've tried 3 cards.  Our system thinks 2 of these cards (4844 and 5843) are registered in Brazil, and the other (8722) is registered in the UK.

Because originally you got a lot of these 'COUNTRY_MISMATCH' errors, our system barred the users.  To prevent testers getting 'barred', Tom changed the account type from 'End user' to 'CP' (content provider) - while this does prevent users being 'barred', it also circumnavigates the country check.

Because of this certain users (the ones that have been set to 'CP') have been  been able to make purchases with cards registered in another country.  Of course for other users the country check still applies and they will be declined (this explains why it worked for Karina and not for Rodrigo). 

This is not a bug and is expected behaviour - you need to use a local CC for testing on stage.

Comment 14

[krupa raj[:krupa]]

(In reply to Keir Kettle from comment #13)
> Background - for end users the Bango credit card system doesn't allow credit
> card purchases with cards registered in another country, and if you get
> multiple declines the system will stop offering credit card as an payment
> option (to prevent fraud) by 'barring' the user.
> 
> You've tried 3 cards.  Our system thinks 2 of these cards (4844 and 5843)
> are registered in Brazil, and the other (8722) is registered in the UK.
> 
> Because originally you got a lot of these 'COUNTRY_MISMATCH' errors, our
> system barred the users.  To prevent testers getting 'barred', Tom changed
> the account type from 'End user' to 'CP' (content provider) - while this
> does prevent users being 'barred', it also circumnavigates the country check.
> 
> Because of this certain users (the ones that have been set to 'CP') have
> been  been able to make purchases with cards registered in another country. 
> Of course for other users the country check still applies and they will be
> declined (this explains why it worked for Karina and not for Rodrigo). 
> 
> This is not a bug and is expected behaviour - you need to use a local CC for
> testing on stage.

For Seahorse, is the plan not to support International credit cards? how will we avoid the country mismatch error in that case?

Comment 15

[Steve Ruston]

Krupa, my understanding is that it is to support credit cards that allow international payments not international credit cards. But I default to David B's knowledge

Comment 16

[David Bialer [:dbialer]]

My understanding has always been that the origin of the credit card must match the region in order to prevent fraud and Keir describes.  So for instance, if a user holds a Seahorse originated credit card (highly unlikely) then any Seahorse purchase should be authorized.  If the card if from the USA, it will be rejected as it is considered likely fraud.  

What I go back to Keir on is whether the country match is based on the store region (i.e. Seahorse) or the geoIP address?  So for instance, could I use a US credit card from within the US to purchase an app in Seahorse?  

The GeoIP would be preferred since we would like to allow users in one region to purchase apps from another region.  Unlike other apps stores, users are not restricted by country as to which store they can visit and should be able to purchase from.

Comment 17

[Keir Kettle]

(In reply to David Bialer [:dbialer] from comment #16)
> The GeoIP would be preferred since we would like to allow users in one
> region to purchase apps from another region.  Unlike other apps stores,
> users are not restricted by country as to which store they can visit and
> should be able to purchase from.

The country match is based on the IP / detected network of the user and not the region of the store.

Comment 18

[David Bialer [:dbialer]]

Thank you Kair.  This how I expected it work and the 'correct' way in that it prevents frauds when CC's are used out of control but allows in country usage of the card.  Thus, for instance, if I live in the UK but want to make a purchase from Colombia, you should be able to do this as long as you are in the UK using a UK credit card.  You would be charged in COPs and might have to incur some exchange fees from your bank

The behavior in this bug seems correct and it does what it is supposed to do.