Automatic Payment Reversal

General

LoanPro and Secure Payments (formerly PCI Wallet) can automatically reverse payments that are not successful. This function is relevant to ACH/EFT/eCheck payments, NACHA returns (requires an import), and credit card chargebacks. These payments will initially "succeed", but may be reversed due to insufficient funds or a customer-initiated action. This function is also only natively available if you are using Secure Payments in association with LoanPro. If you are using Secure Payments' API with your own application, you will need to use the Transaction Status Callback to make your application aware of failed transactions. You can then handle the reversal in whatever way you choose.

Set Up Automatic Payment Reversal

Transaction Status Updates

In order to set up an automatic payment reversal between LoanPro and Secure Payments, first, make sure you have the  Transaction Status Update URL set correctly in the events section of Secure Payments. The correct URL is https://loanpro.simnang.com/api/public/thirdparty.php/pciw/transaction-updated/callback. This will notify LoanPro when a transaction status changes in Secure Payments. Use the toggle switch to make sure the callback is on.

Processor Settings

It's also necessary to turn on automatic payment reversal for the processor. This should be done inside of LoanPro by navigating to Settings > Company > Merchant > Secure Payments.

To change the setting, click edit edit to edit a processor.

Make sure Auto Reversal is set to Yes and click .

Updating Transaction Statuses Through the API

You have the ability to update payment statuses using your own application through the Secure Payments API. Instructions on how to do so are found in the Secure Payments API Update Transaction Status article.

NACHA Return Codes & Canada Return Codes

NACHA processors also have an Auto Reversal setting. This works based on the return file you receive after submitting a NACHA file for payment processing. This file will give a NACHA return code or "R Code" for each returned transaction. LoanPro lets you specify what the effect of each R Code will be. For more information about configuring your R Codes, see this article. Canada Return codes function the same way as "R Codes" and are setup up the same way. For more information regarding Canada Return codes, see this article.

The diagram below shows the process for making NACHA payments.

The step we are looking at is "Send the return file to Secure Payments to update the transactions." This can be done in two ways. The first is to use the Secure Payments API to update the status of transactions. The second is to import the returns file as a CSV into Secure Payments. This will update the status of the transactions included in the return file.

Upload a Returns File (For NACHA Processing)

Create Import File

To upload a NACHA returns file and update the transaction status of NACHA payments in Secure Payments,  first navigate to the Import section of Secure Payments and select the  button in the top right-hand corner of the page.

In the Import information window, select TRANSACTION UPDATE then Download the sample file. This will download an import template file to your computer. This template file will contain all of the headers necessary for your import and also some example information as shown below.

Row one contains the headers for the import, and row two contains the example information.

To build the import file, fill in the id column with all the id's of the transactions you would like to update. Because this is a return code import to update the R-Code of failed payments, fill in the status column with FAILED for each transaction. Fill in the R-Code column with the corresponding R-Code for each failed transaction id. For more information on R-Codes see this article. The Comments section is not required but may be filled in with comments for each failed transaction. Below is an example of what your file should look like.

Once you have entered the correct information in the file, make sure to save the file and take note of the location of the files on your computer.

Note: You can import Canada return codes for CPA005 processors/transactions as well.

Import File

Back inside of the Import section of Secure Payments select 

First, choose Transaction status update from the "File type" drop-down.  Now drag and drop the file in the drop zone, or click the drop zone to find the file on your computer. Here you may also specify who will be notified when the import is validated and completed using the "Notification Email Address" field.  If you select "Address on account" the notification email will be sent to the email associated with your Secure Payments account. If you select "Custom" another field will appear where you may enter a different email address where you would like to receive the notifications.

Once you have the file ready to be uploaded select SAVE  .

When you finish your upload, you should get a window telling you the upload was successful. Click  

You should now see your upload in the list of import uploads in Secure Payments.

If there are any errors in your file, the Verified column of the list will say No next to your file. You will also receive an email notifying you that the import validation failed. This email will contain a file with a list of all errors in your import file. You may also download this error file by selecting   next to your import file in the Verify File column. If your file contains errors, you may fix the errors and download the file again. If the file is error free, Click to upload it. Your import is now complete.

Note: For information on how to upload a returns file through the API, see the Upload & Validate Returns File section of the  NACHA Process Start to Finish article.

Reversal Fees

You can choose to have LoanPro automatically log a fee for reversed payments. This is done by setting up a  recurring fee that is based on the payment reversal event. To do this, navigate to Settings > Loan > Charges > Recurring Charges in your LoanPro account.

Click  ADD .

Make sure the Trigger Type and Trigger Event are sent to "Event" and "Payment Reversal" respectively. You can set up the charge as you like, including specifying an R Code that will trigger the charge.


How did we do?


Powered by HelpDocs (opens in a new tab)