Moving Credit Card Vault Data

We are moving from Paya (the Sage credit card processor) to another vendor. Our new processor has asked us to request a .CSV file from Paya of our credit card "vault". Paya (who stores the "vault" information) does not seem to want give us this data. Has anyone else dealt with this, and what was your work around?

  • 0

    A properly integrated solution will work with an installer, so I'm assuming you're going with a completely external system (not integrated with Sage 100).

    We did this once when it was SPS (before being sold and rebranded as Paya).  Have Paya talk directly with the 3rd party to come up with a plan.  CC data in a CSV file is not secure / PCI compliant.

  • 0

    Yes, we are going with a completely separate provider. They told us that Paya would not interface with them and that we would need to be the intermediary. I spoke with Sage, which was completely hands off, then reached out to Paya who told me that we would need to have every card holder sign an authorization form to have their data released. My frustration is that this must happen every day, whey is there not a clearer path?

  • 0 in reply to Matman

    What use is a secure data vault if a business process can bypass it all and produce a file with all the "protected" data?

    If the volume is not excessive, do it with manual data entry, one card at a time opened using the Sage 100 regular interface.  Painful but it works.

  • 0 in reply to Matman

    ...or consider an integrated service provider.  There are a few.