My first post here and a few days in using the system. I do believe I am in love (as far as anyone can love an accounting system) with Quickfile.
I run an online business selling intangible products. Our customer base is diverse and I am a tight git!
I have integrated GoCardless for their low cost bank transfer payments (for UK and soon EU customers) in the process of sorting out BitPay for the few customers that might pay that way and am pushing those to my customers as preferred options to pay be.
But…
Many of my customers are based in the US. I have no problems (yet) from the accounting side but if I were to integrate options such as Dwolla or other US specific payment options or merchant accounts; is it possible to show only preferred payment options per geographic location of my customers?
Hi Jason, I’m pleased to hear that you’re getting on with Quick File!
You can actually set payment option defaults per customer and this can be achieved in the client settings area. It works on the basis of exclusion, so you’d need to select those payment options you want to disable for given clients.
Admittedly this needs to be done on a per client basis, so unfortunately there’s no way to set defaults by country. I’ll leave this feature open and if it garners more support we can look at further automation here.
Ahhhh I couldn’t see for looking and that’ll do the trick
I am looking to automatically add clients, invoices etc via the API so I presume this can be done there too? (Not a problem if no as I will build a small function to emulate the equivalent clicks)
One other, related, question though:
IE - I’d like to add Transferwise, Dwolla or potentially WorldFirst etc for those non EU client.
I’ve read through the API docs and although I may have missed it, I don’t specifically see a way to add a payment option that isn’t already supported. Am I missing something or is there a universal web hook or equivalent?
Setting payment restrictions isn’t in the API right now but it’s in the process of being added, so should be there in a couple of weeks.
Those additional payment processors aren’t currently supported I’m afraid, the ones we support are listed in the payment options screen. We may add them in future if there is a certain demand there from other QF users. Otherwise we are happy to extend our API to allow developers to build their own integrations, this would be out preferred approach as we simply don’t have the resources to develop all options internally.
Hi,
First I’d like to echo Jason’s praise. I’ve been using Quickfile for a couple of days and I must say I’m impressed.
I’d also love to add other pay methods, particularly Transferwise. The current solution to integrate payments through it in Quickfile is not ideal. So if there’s an app being made or a project in view for integration of extra methods, I’d love to hear about it.
We would certainly like to add more payment options to QuickFile, the problem we have is each integration takes a good chunk of time to build, test and deploy. Not only that but we often need to open accounts with each provider to maintain the integration and upgrade when necessary.
It strikes me as odd that a service is yet to exist that allows a payment token to be posted to a single aggregator that would then reveal a host of configurable payment providers. That way we would essentially just integrate with that service as if they were a single payment provider. Perhaps this exists already I’m not sure?
One idea we have discussed in the past is to build a data connector, something that will be simpler to integrate than our full API where you can design templates for posting the data (XML, JSON, HTTP Variable etc) to the chosen payment provider. We could then allow users to share these templates online, this will enable us to offer much wider support for all the different payment providers, and there are certainly more and more of these appearing all the time.
