Authorize.net documentation leaves much to be desired.. In order to implement Google Pay, which they call Android Pay now, they require that you create a Signature Key.. In order to create the Signature Key they ask that you enter a KeySet ID.. However, no where in the documentation and I haven't found anywhere online that it actually explains what a KeySet ID is or what Authorize.net thinks it is, where it can be found or how it can be created.
I have tried to pass along a Google Pay transaction to Authorize.net without any kind of Signature Key or anything and in the Google Pay TEST environment.. The result was an error from Authorize.net:
"errorCode": "153",
"errorText": "There was an error processing the payment data. Unable to decrypt data."
Related
I'm using Amazon Selling Partner API to import orders in my application.
I'm using orders/v0/orders to get the orders list and foreach order returned I call
/orders/v0/orders/{orderId}/address to get shipping address
/orders/v0/orders/{orderId}/orderItems to get items in order
/orders/v0/orders/{orderId}/buyerInfo to get buyerEmail and buyerName
Now, the last thing I need is to get the eventual billing address.
I search in SP-API documentation but I didn't find anything useful.
Can someone help me?
I don't think it is possible. This was asked regarding MWS and the response was "why" given that Amazon handle all billing. I suspect SP-API is similar.
https://sellercentral.amazon.com/forums/t/retrieving-buyers-billing-address/124948
I have a Django Saleor based website which is using stripe.js to manage the payments. During the checkout process, I am collecting the billing address as part of the checkout process but once I enter valid card details (even though billing address is incorrect) the payment is still successful. On the stripe dashboard I can see that the street and postcode check failed but the payment is successful. Anybody know how I can enable this.
My end goal is to make sure where the billing address doesn't match, these transactions are declined.
If you want to block charges on cards with an invalid ZIP code or an invalid Line 1 address, the best solution is to use Radar rules. This is documented in: https://stripe.com/docs/radar/rules#traditional-bank-checks
Suddenly, today, I could not continue to perform ItemSearch queries on the Amazon Product Advertising API.
This is the complete XML error response I get.
<element '{http:="" ecs.amazonaws.com="" doc="" 2005-10-05="" }itemsearcherrorresponse'="" at="" 0x7f58cc173138=""></element>
Error responses usually come with additional information in a Code
field, that helps understand the cause of the error. But not on this case.
Have I been blocked? or Does this mean the service is down momentarily?
As per I have understood, Amazon has suspended access to the Product Advertising API since the beginning of July.
You can ask for a restoration of your access, but owing to what I have been able to read on the web there are very few exceptions.
I have followed the steps detailed here: google oauth2 how to get private key for service account
But everytime i try and create a service account the process fails. The error message is an unhelpful "Sorry, there’s a problem. If you entered information, check it and try again. Otherwise, the problem might clear up on its own, so check back later."
I have waited a full 24 hrs and the problem has persisted. Can someone please help.
Edit: I want to create a p12 key but i have tried generating both json and p12
I am using the Amazon product Advertising API to fetch the product categories. For US categories it is working.
But using browse nodes from different sites I get the following error:
"569604 is not a valid value for BrowseNodeId. Please change this value and retry your request."
I got the browse-nodes from the following site:
http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/index.html?BrowseNodeIDs.html
Where is the problem?
Thanks for your help!
This is an error that happens pretty regularly with the Products API, but not because the BrowseNodeId does not exist. Rather, the API intermittently craps out and returns this error. If you run it again, it will probably return the node correctly.
The way I have gotten around this limitation is to wrap the call in retry code.
Edit.
I tried running this BrowseNodeId, and indeed, it is invalid. The BrowseNodeIds change regularly, and because this is a german browse node you may not be able to access it from the US.
However, according to this, your BrowseNode (Electronics, DE) should be available in the US:
http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/APPNDX_SearchIndexValues.html
You can test browse nodes at this url:
http://www.amazon.com/exec/obidos/tg/browse/-/$N/
where $N is the browse node.