ProPayVault

Setting up the ProPay Vault

To have a ProPay vault created you will need 4 documents filled and signed by the client in question.

The documents will be found on .11 within their own client folder, if they do not have a client folder you can copy the NewClientBase, create their folder. The documents are apart of the base folder. The 4 document names will be "ProtectPayAgreementv1.2022.pdf", "ProtectPayflatrateScheduleA.docx", "EFTFormforProPay.pdf" and "w9.pdf".

The ProtectPayflatrateScheduleA.docx document will need to be filled out manually and saved to a PDF before sending. The other 3 document fields will be filled out when sending the documents to the Clients VIA DocuSign. DocuSign has a very intuitive way to add fields and require the fields when filling out the forms/documents to send to the client.

Once the documents have been signed VIA DocuSign by the client you will download the signed documents, upload them into the .11 client folder and send them to your contact at ProPay. At the time this was written you would send it to Marda and/or Heather at ProPay. You will also send Heather or Marda the Merchant Processor information for them to connect to, this is either the Login ID and Password or will be API keys depending on if they are going with Auth.net or NMI.

You will receive an MPID and 2 keys from ProPay, all 3 will be updated in the client settings table in SQL. The MPID will be added to the setting named DefaultMerchantProfileID, the basic key will be added to the PCIWebserviceAccount and the secret key will be added to the PCIWebserviceKey.

Once you have added these settings values you will want to test the vault by processing a $1 transaction through the system. Errors will need to be reviewed with ProPay to figure out where in the process it is breaking down. Once the $1 transaction is successful the vault is setup.