Closed
Bug 864878
Opened 11 years ago
Closed 11 years ago
Incorrect amount is billed to mobile bill in Spain - tax is being double billed to user.
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-05-02
People
(Reporter: dbialer, Assigned: jorgev)
References
Details
Attachments
(2 files)
Purchase was made on direct bill of apps for .89 euros. This is inclusive of spain tax of 21%. Instead, 21% was added on top of the .89 Euro price to bill user for 1.08. I suspect this is a problem for all price tiers.
Reporter | ||
Updated•11 years ago
|
Version: 1.2 → 1.0
Updated•11 years ago
|
Blocks: marketplace-payments
Comment 2•11 years ago
|
||
We will raise with telefonica.
Comment 3•11 years ago
|
||
Response from Telefonica: Yes, it is like Antonio said. Spain configured the account to add taxes locally. The accounts in preproduction are standard testing ones, so maybe we did not notice there. Anyway, we need to get the amount without taxes so they are not doubled. Best JORGE El 24/04/13 15:25, "ANTONIO JOSE LOPEZ NAVARRO" <antoniojose.lopeznavarro@telefonica.com> escribió: >Hi, > >Yes, Spain add taxes to the amount we send them. In order to have taxes >correctly added, we just need to receive the amount w/o taxes into our >API. Don¹t know if it was required for Mozilla, but it is for the >previous integration: > >https://bvpartner.tid.es/redmine/issues/2249 > >Regards, >Antonio
Reporter | ||
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
will be deployed by Bango in time for US day 30th April
Comment 6•11 years ago
|
||
Deployment done for this fix
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 7•11 years ago
|
||
Reopened until Wifi is fixed Hi Steve, The changes are now Live. I have sent a couple of transactions and we can see that we are sending the right amounts. For requests when the user is on a Carrier connection, which use the Mobile Id Identifier, the billing the request is processed correctly, but using the MSISDN which is used for the Wi-Fi Flow BlueVia is returning an error, stating that we should be using the mobile Id. I’ll have to forward this to BlueVia for analysis. As such, while you can proceed with the testing on 3G, the WiFi is on hold until it’s fixed by BlueVia. Here is the detail of a 0.15 EUR transaction, as you can see we are sending 0.12 (Gross Price) to BlueVIa, while on our end the transaction is recorded as 0.15 (Net Price). MOBILE ID · Request <?xml version="1.0" encoding="utf-8"?> <pa:paymentRequest xmlns:pa="http://api.bluevia.com/schemas/payment/v2"> <userId>mobileid:c2cf4d609410e155fa794eabf80faJDT</userId> <description>Mozilla - A name for the number</description> <amount>0.12</amount> <currency>EUR</currency> <channel>WEB</channel> <referenceCode>f6213631-f555-4ec0-953d-3787d187a9ec</referenceCode> </pa:paymentRequest> · Response <?xml version='1.0' encoding='UTF-8'?> <wstxns1:paymentStatus xmlns:wstxns1="http://api.bluevia.com/schemas/payment/v2"> <wstxns1:paymentMethod> <wstxns1:type>directToBill</wstxns1:type> </wstxns1:paymentMethod> <wstxns1:transactionId>07c00358-0ac6-4284-be69-3f19480f5d66</wstxns1:transactionId> <wstxns1:status>charged</wstxns1:status> <wstxns1:statusDate>2013-04-30T10:27:29.156Z</wstxns1:statusDate> <wstxns1:referenceCode>f6213631-f555-4ec0-953d-3787d187a9ec</wstxns1:referenceCode> </wstxns1:paymentStatus> WIFI FLOW – Uses MSISDN · Request <?xml version="1.0" encoding="utf-8"?> <pa:paymentRequest xmlns:pa="http://api.bluevia.com/schemas/payment/v2"> <userId>tel:34628661469</userId> <description>Mozilla - A name for the number</description> <amount>0.12</amount> <currency>EUR</currency> <channel>WEB</channel> <referenceCode>55bf7d4e-12df-4406-966d-27c1d36b4afa</referenceCode> </pa:paymentRequest> · Response <?xml version='1.0' encoding='UTF-8'?> <wstxns1:exception xmlns:wstxns1="http://api.bluevia.com/schemas/common/v2"> <wstxns1:exceptionId>SVC1021</wstxns1:exceptionId> <wstxns1:exceptionText>Invalid parameter value: userId. Supported values are: mobileid:xxx</wstxns1:exceptionText> </wstxns1:exception>
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Assignee: keir → jorgev
Assignee | ||
Comment 8•11 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=865639 Configuration has been reviewed, it should work now. Best JORGE
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → INVALID
Updated•11 years ago
|
Resolution: INVALID → FIXED
Updated•11 years ago
|
Target Milestone: --- → 2013-05-02
You need to log in
before you can comment on or make changes to this bug.
Description
•