Use caution.
These type of 3rd party web integrations seem to always start this way ( easy-peasy, no need to integrate to Sage )
Then in x months, there's a need
Then in x months and 6 days, the 3rdparty developer lays the blame on why it can't happen at Sage's feet and announces that they've gone as far as they can ( stop me if you've heard this story before )
Then in x months and 6 days + 30 minutes you get the call from the customer asking how you are going to fix it
If your practice is like mine, you wake up to discover you were led into a free complimentary suggestion of how to integrate credit cards 6 months ago to the whole project being your responsibility and expectation that you'll call Sage Paya and work tirelessly to solve a problem that you didn't create and likely advised against at the start.
My observation:
- I have a customer who collects the cards external to Sage using Paya
- The 3rd party can get the card into the Paya vault ( it creates a GUID )
- The tricky part seems to be syncing the vault with the Sage 100 credit card file on the local server
I have found these types of easy web requests take on a life of their own and inch by inch you are drawn into becoming the UNPAID service and warranty department for a project that you may not have been initially paid for.
These are actually very high-value consulting engagements that I find myself giving away too much knowledge. The customer doesn't appreciate it because they consider this type work "table stakes" and if/when you refer to a 3rd party ISV most don't pay commission on consulting or if they do it's maybe on the first engagement ( if lucky ).
I'm rethinking how I approach these because I personally keep getting drawn into a bunch of freebie type engagements.
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------