Payment profile import – Secure Payments
This is the first step in the two-part process of importing payment profile information. Here, we describe how to import information into Secure Payments. After completing this step, the information can be imported into LMS. If you are ready for the second step, feel free to skip ahead to our payment profile import – LMS article.
Occasionally, you may need to enter a large batch of payment profiles into Secure Payments or LoanPro's Loan Management System (LMS). Entering each payment profile manually is not only time-consuming, but it could lead to entry errors. Instead, you can add large quantities of payment profiles with ease by using the import tool.
To maintain PCI compliance, full payment profile information can only be manually input or imported into Secure Payments. Once the payment profile is entered here, an automatically-generated token is created. These tokens ensure sensitive payment information is kept secure in the event that your account is compromised. In terms of importing payment profiles into LMS, only the tokenized payment profile information can be used. This is why we have broken the payment profile import process into two steps: importing into secure Payments does not require a token, while importing into LMS does.
In this article, we will exclusively explain how to import payment profile information using Secure Payment's import tool.
Multi-factor authentication
If you have multi-factor authentication set up already, you can skip this step and head to Creating an Import File below.
The first step to importing payment profile data is setting up multi-factor authentication (MFA). If you're unfamiliar, multi-factor authentication adds an extra layer of security to your login process: Instead of just a password, you'll need a password and a code from an authenticator app (usually on a smartphone or other device). If you don’t already have a multi-factor authentication app, we recommend using Google Authenticator.
With an authenticator downloaded on your smart device, you're ready to set up your authentication. The process is easy, and Secure Payments will walk you through the setup within the software. In your Secure Payments account, navigate to Profile > MFA Settings. You will first be asked to enter your Secure Payments username and password.
Next, click 'Submit'. You'll be shown a QR code that you can scan to add Secure Payments to your current multi-factor authentication app.
On your device, scanning the QR code with will prompt your authenticator app to open, where you'll see a six-digit code. Enter the code into the field in Secure Payments and click 'Submit'. Now, you will be able to import payment profile information.
Creating an import file
The easiest way to create an import file is to use the templates we provide. To download the template file, navigate to the Import section in Secure Payments and click the blue information icon, highlighted in red in the image above. Clicking the icon will pull up this window:
The window has three tabs at the top for importing checking account, bank card, and transaction update information. Each tab provides instructions as well as a download link for an import sample file. We recommend using these files to ensure your information is formatted correctly. You can download each template from it's respective tab, or you can download them below:
Each sample file is a .csv file formatted like this:
The first row of the sample file includes the available headers. The second row contains example information for all the required fields.
The available fields for the Bank Account import file are as follows:
| Field | Example | Description |
| profile_id | 1264 | This is the ID of the profile. |
| account number | 12697531 | This is the account number of the bank account. |
| routing number | 124002971 | This is the routing number of the bank. |
| eft branch number | 003 |
This is the branch number for a Canadian bank. This is only for Canadian bank accounts. |
| eft institution number | 0BBBAAAAA |
This is the institution number for a Canadian bank This is only for Canadian bank accounts. |
| bank name | Wells Fargo | This is the name of the bank. |
| address | 123 Oak Lane | This is the address that the account holder has on file with the bank. |
| city | Schenectady | This is the city the account holder's address is located in. |
| 2 letter state code | NY |
This is the state the account holder's address is located in. This will be a two-letter province code for Canadian accounts. |
| zipcode | 12345 |
This is the zipcode of the account holder's address. This will be a postal code for Canadian accounts. |
| 3 letter country code | USA |
This is the country the account holder's address is located in. 'USA' for the United States of America; 'CAN' for Canada. |
When you import bank accounts into Secure Payments, the import does not validate the routing numbers; it simply checks to make sure they are nine digits long.
The available fields for the Bank Card import file are as follows:
| Field | Example | Description |
| profile_id | 1264 | This is the ID of the profile. |
| cardholder name | John Doe | This is the name of the cardholder. |
| expiration date | 02/26 |
This is the expiration date of the card. Formatted as MMYYYY. |
| card number | 4000 1111 2222 3333 | This is the number of the card. |
| address | 123 Oak Lane | This is the address the account holder has on file with the bank. |
| city | Schenectady | This is the city the account holder's address is located in. |
| 2 letter state code | NY |
This is the state the account holder's address is located in. This will be a two-letter province code for Canadian accounts. |
| 3 letter country code | USA |
This is the country the account holder's address is located in. 'USA' for the United States of America; 'CAN' for Canada. |
Each row in the file represents one payment profile. Once you have entered the information for the payment profiles you want to import, save the file. Then, back in Secure Payments, click the large plus icon to import your newly saved file.
The data you enter into your import files may include leading zeros. Leading zeros is a piece of data that begins with zeros, such as an ID like "00045789". Excel tends to drop the zeros in this data since it thinks you won't need them, but they are often crucial to ensuring your data is accurate.
Importing your file
To import your file, first choose whether the file you are uploading contains bank accounts or credit/debit cards from the “File type” drop-down. You can 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 the email address where you would like to receive the notifications. Once you have specified which file to upload, enter the MFA code generated from your multi-factor authentication app. Finally, click 'Save' to finish.
When you finish your upload, you will receive a message notifying you that the upload was successful. You should now see your upload in the list of historical imports.
If there are any errors in your file, the file will not be verified. If an error occurs, the upload will display "No" under the Verified column. 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 can also download this error file by clicking the download icon 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, complete the import process by clicking the cloud icon to upload it.
Now that your payment profile information is imported into Secure Payments, you can transfer the tokenized information to LMS. To learn how to import into LMS, read our payment profile import – LMS article.
Was this article helpful?