Hi again,
Customer asked a question where I am not sure who to call first and am loathe to start by calling Sage support before getting to the right person.
We currently use the following workflow:
- Credit cards are preauthorized on the website (their custom website talks to Paya to do pre-auth, uses custom boi to add sales orders to Sage)
- He wants to be able to just send no credit card info over to Sage to avoid having to send the full credit card number again and wants to know if this will work
Does Sage actually require the original card number (PAN) to complete the capture, or can the capture be completed using just the Paya token and the original authorization reference?
If the PAN field must be populated in Sage, is it:
- Actively validated/used during capture, or
- Required only to be present due to legacy field requirements?
I am trying to talk him into to testing this out himself by entering a test order on the web and altering the data before he sends it to Sage and substituting ****1234 for the card but he says he won't until he can definitively hear he that you can use it. Assuming the asterisks really represent an encryption and not just plain asterisks that have to match what is in the vault.
TIA
Christine
------------------------------
Christine Kuhn
Consultant
RKL eSolutions, LLC
------------------------------