I create Field55 to make emv transaction from NFC-terminal, all work fine but it's need to set by what method user make pay: token (Apple/Google Pay) or by physical card (pan). I know how to get it when read payment but, but can not find which tag in filed55 responsible for this information. If anyone know - please help. Thanks!
It's a little hard to understand what you are doing. Card emulation on tokenized wallet transactions in face to face interface produces exactly the same data as for any other card. If you are trying to produce face to face transactions from ecommerce tokens - it's not possible as this will generate in best case a 3DS cryptogram, not EMV data (with an irrelevant exception).
Can you maybe explain better what you are trying to achieve?
Related
So Stripe support is currently not able to answer my questions. I have a Wufoo form set up and Stripe subscriptions tied to it. Well I have mapped the product values in the Stripe subscriptions to my form values.
However, I am not looking at an open field for a donation form to let a user define a price. Stripe support can't seem to find an answer. My assumption the support staff is combing their documentation and Google to find an answer and they can't, the same as I have.
That said, does anyone know if you can pass an open value to a Stripe subscription.
In essence letting a donor define the price they want to pay monthly.
So I checked with Wufoo and through them, the answer is no. Not right now. You can not add an open value. I have seen other systems using Stripe in which they allow open values, which means it is possible, but I guess not through Wufoo and you will probably have to write your own subscription code to handle it.
Our Team is currently working on a car routing web application with the HERE-API. To meet the users expectations, we want to integrate all the typical features everyone is used to nowadays, most importantly the possibility to manipulate a route interactively by dragging waypoints out of it.
While for the most part everything seems to work fine, we are experiencing serious performance issues on long routes combined with large drag distances.
Our applicaton works a follows:
-at first the user has to provide two addresses
-the route is initially calculated using a full calculateroute request (representation = 'display')
-now, when the user drags the route, we request a new route with a waypoint at the mouse position and reduced response data (representation = 'dragNDrop') every 500ms for the time the dragging process lasts
While this procedure is working really well and fast when zooming in to a small section of the route, it is very slow and laggy when zooming out to country size and dragging while the whole route is being displayed. Implementing a throttling mechanism and experimenting with different call rates helped a bit, but not as much as we hoped.
Having a look at the constant performance on wego.here.com, we were hoping that there might be a better way to implement this feature with the HERE-API or maybe some kind of optimization.
We would very much appreciate any help.
Routing API will provide the best solution with respect to the use case. can you please share the API response time or full API request. please check clustering document if it aligns with the use case.
developer.here.com/documentation/maps/dev_guide/topics/clustering.html
if it does relate to the number of request(which cause the implementation of throttling and increase API requests), please connect us at
developer.here.com/contact-us
Thanks for your reply! It had been pretty crazy this year so this post is a bit late - my apologies for that.
The solution to our Problem was a small adjustment to a parameter value. We lowered the value of the parameter 'resolution' to '25:25' for calculateRoute-Requests while doing route draggings.
I'm currently evaluating using Plaid or Yodlee for transaction aggregation (I'm using the Dev environments for both right now). I really prefer almost everything about Plaid, but I'm having trouble with transaction name/description. Yodlee has a data field called the "simple description":
From their docs: "The transaction description that appears at the FI site may not be self-explanatory, i.e., the source, purpose of the transaction may not be evident. Yodlee attempts to simplify and make the transaction meaningful to the consumer, and this simplified transaction description is provided in the simple description field."
I'm displaying the transaction name to my end-users and I'm looking for something more user friendly than the transaction name field which often returns strings like "Withdrawal Check Card MOE'S BROADWAY BAGE BOULDER CO Date 01/06/19 0 9006020339 0 5812 Card [XXXX]".
I'm sure I'm not the first plaid customer to have this need. How do Plaid reliant apps solve this problem?
Plaid doesn't offer a simple description field as far as I know, but they do clean up transaction names.
I've found that when a new pending transaction comes in, the name is messy like you mention (e.g. UBER *TRIP 5VVB2). But once the transaction is confirmed, Plaid normalizes it for common merchants (e.g. Uber). I don't know why Plaid doesn't offer this normalization for pending transactions, but I have brought it up with them before. Perhaps this is something that could change in the future?
A solution, albeit complicated, is to build a custom model that normalizes transaction names. That's what we are doing at Pluto Money to supplement Plaid's transaction data.
I received a direct response by email from Plaid Support:
Thanks for reaching out to us here on Plaid Support, I'm sorry about
our delay.
Our name field for each transaction represents our best effort to
balance detailed transaction information while providing a clean and
consistent API response. This behavior does vary across banks, both
due to bank behavior and our own integration quality. Generally at
larger banks our integrations do a better job at returning clean
transaction names with appropriate transaction detail but for some of
our smaller banks transaction names may be more "raw".
If you never want additional detail beyond the merchant/transaction
name in your app I would encourage you to implement some filtering on
Plaid's name field to make sure that no date- or account number-like
character strings pass through into your user facing stream.
This is more of a general programming question.
I'm trying to create an app, think of it as a Yelp clone. I have most of it working but I'm missing one important feature. The data of the places around me. For now I'm only focused on food, so I'd like it if I search something like "Pizza", it'd show me all the pizza joints near me.
I was originally planning to use Google Places API. However if you havent heard, they're changing their pricing and lowering the free tier and upping the cost by a huge margin.
There's also the problem of saving the data. One workaround I saw a user suggest was to just keep using Google's API, but every time you make the query, store the data in your own DB as well (I only need address and name and latitude and longitude) so eventually, you'd have what you need in a sense. However I also want to have something like a simple rating system for each place like Yelp, but Google (and all other places like MapBox, Here Maps, etc) states something along the lines of "info from their API should not be stored or cached for more than 24hrs" but it's very broad and not specific.
So what I was planning to do was, call the Google API, grab the 3 info I need (Address, Name, Lat/Lng), add more fields to store the rating, likes, whatever else the user will add. Then store it in my database, but that doesn't seem like a solution now.
So does anyone have any ideas or advice? Or know of a service where I can get the details of all the food places? And if possible, can anyone confirm that storing the Name, Address, Lat&Lng is a violation of their policy since in my eyes, it's public data, but something like the rating that Google provides, or the pictures that Google provides, now that's Google property.
For obtaining places you can use OpenStreetMap, e.g. using Overpass API. Since larger traffic can be expected you should run your own database(s) instead of using the public APIs.
However OSM doesn't contain ratings. So you have to combine this data with some other publicly available rating system.
I am one of the web developers for a small-but-growing e-commerce site. It is now getting about 150 orders per day, and a lot more on Cyber Monday. This is enough volume so that the small fraction of users who have hard-to-reproduce problems are causing significant heacache. My theory is that one of more of the following are true:
The customer is on an unusual browser / OS
The customer experiences a network glitch
The payment gateway takes too long to return a response
The customer somehow hits escape or the back button during a critical moment in the ordering process
The customer closes their browser
The customer's browser just refuses to navigate to the next page
The end result of these problems is usually that a customer unknowingly gets their credit card charged, and often attempts to place a second order. In that case a refund has to be issued on one of these duplicated transactions.
Although I would like to convince my client that there will always be a "normal" percentage of orders that have "weird" glitches, I don't know what "normal" is.
My question is therefore:
In your experience as an e-commerce developer,
what is your observed rate of these glitches?
Alternatively, if you can point me towards statistics, that'd be helpful, too! I haven't been able to find any.
Thanks!
ps. I know that it would be ideal to fix the root cause of such problems, but I simply have not been able to reproduce the problem, even after submitting hundreds of test orders.
You know the old saying - "If you have to ask, you can't affort it"?
It applies here.
It's very likely that your problems would be caused by the reason you listed above - apart from any bugs in your code, of course.
But is that a good enough explanation for your client? As the application traffic increases these problems are likely to increase as well.
You may need to implement a more robust process that can handle unexpected problems, so that customers are not charged unless you have captured their order or they are notified by email that their order completed / something went wrong / what action they should take.
edit:
Your question is when to stop improving the website. I think this depends on the level of service (read: time) you want to give to your client vs their expectations of what they have paid for.
How you deal with it forms part of your business strategy, but my approach would be to very honestly show them a list like this with time estimates to fix each item. Ensure they understand the diminishing returns that each of these fixes achieves. Give them something for free, and charge them for anything else. Negiotiate with them; give them a KPI or performance target that you guarantee to meet. It's important that they understand the costs involved in designing a near-perfect transactional system.
Rather than guessing, I'd try to assert how the errors are raised, build a simple form where users can leave you the browser they used, system specs (maybe) and the steps to reproduce the defect that araised.
Then with that information you can debug your app, make unit tests and fix these bugs, or reduce them to a form where they won't impede your users from buying stuff at your site.
Usually it is just one or two people with weird cards or weird browser/OS combo that cause all the headache, while all "normal" people proceed fine.
You better switch to a gateway that supports background processing (customer always stays on your checkout page while order info is packed into XML and posted to the gateway, and it instantly responds with any errors) - this will at least eliminate navigation problems for dummies.