Settings and activity
2 results found
-
34 votes
It is certainly a nice idea in a lot of ways, and Jesse’s use case example is good one.
On the other side, allowing 3rd party applications plug into the core Xero application present some quite major security implications. The data we hold on behalf of our customers is considered highly sensitive by us and we ensure we have bank level security across all aspects of our application.
Second to that, we are a design lead and focused company – we want our software to be really easy to use and remain simple and intuitive, so allowing 3rd parties to introduce interface elements into Xero would be something we would need to carefully plan for.
With this in mind, it would be quite an onerous task for us to implement a secure framework that would allow 3rd party applications to interface within Xero, in a sensible way that does not…
Roberto Moreno
supported this idea
·
-
50 votes
I think it is a good idea to close this suggestion out as it is not a direction we wish to take for now. Over the next 2 quarters we will be looking to deliver improvements within the application in terms of development of online invoicing and supporting more payment processors, but a credit card payment API is not something we will be looking to do within a 0-3 year timeframe, so declining this suggestion.
Roberto Moreno
supported this idea
·