Secure Payments Events

Introduction

Secure Payments can send information to a specified URL when certain events occur. In this article, we will explain how to add events to your Secure Payments account and provide some of the callback URLs used to link to your LoanPro account.

Adding Secure Payments Events

Full list of available events
Bank Account Create
Bank Card Delete
Bank Card Update
NACHA Batch Generation - Required
NACHA File Generation - Required

User Password Update
Payment Processing
Processor Create
Processor Delete
Processor Update
User Settings Update
Transaction Status Update - Required

To view, edit, and delete events, navigate to Settings > Events inside your Secure Payments account.

Here, you can also use the toggle switches to the right of an event to turn it on or off. To add a new event, click the blue plus icon in the top right.

Next, select the event type for which you want to add a URL from the 'Event type' drop-down. Then, enter the URL in the URL field. You'll notice that each Secure Payments event can have up to 5 callback URLs. Click 'Save' to add the event to your settings.

Required Event Configurations

The NACHA Batch Generation, NAACHA File Generation, and Transaction Status are likely already configured for your account. These three are required, as they communicate to LoanPro's LMS and the database when these events occur. We'll explain how to configure these in the instance that they aren't configured. All other events are optional.

NACHA Batch Generation

If you add the LoanPro callback URL for NACHA file generation, LoanPro will be updated with NACHA batch IDs. The batch IDs are assigned by Secure Payments for transactions processed with a NACHA processor. This is useful, as it will let you pull payments based on their batch ID.

To search by NACHA batch ID, go to Reports > Transaction History > Payment Breakdown.

LoanPro Callback URL:

https://loanpro.simnang.com/api/public/thirdparty.php/pciw/nacha-batch-generation/callback

NACHA File Generation

If you add the LoanPro callback URL for NACHA batch generation, LoanPro will be updated when a NACHA file is generated.

LoanPro Callback URL:

https://loanpro.simnang.com/api/public/thirdparty.php/pciw/nacha-file-generation/callback

Transaction Status

Including the LoanPro URL for transaction status updates will update payments' transaction status as they move through the payment process in Secure Payments.

If a payment is reversed, the r-code is included in the transaction status update callback.

LoanPro Callback URL:

https://loanpro.simnang.com/api/public/thirdparty.php/pciw/transaction-updated/callback

Other Events

As we mentioned above, these events are not required to be configured. But they are available if you'd like to use them. Here's a breakdown of what's available:

Event

Description

Response Example

Bank Account Create

Sends a request when a new borrower bank account is created in Secure Payments.

{
"type": "checking"
}

Bank Account Delete

Sends a request when a borrower bank account is deleted in Secure Payments.

{
"message": "A bank account has been deleted under the Secure Payments account pciwalletaccount@simnang.com"
}

Bank Account Update

Sends a request when a borrower bank account is updated in Secure Payments.

{
"message": "A bank account has been updated under the Secure Payments account pciwalletaccount@simnang.com"
}

Bank Card Create

Sends a request when a new borrower credit/debit card is added in Secure Payments.

{
"message": "A credit card was added under the Secure Payments account pciwalletaccount@simnang.com"
}

Bank Card Delete

Sends a request when a borrower credit/debit card is deleted in Secure Payments.

{
"message": "A credit card was deleted under the Secure Payments account pciwalletaccount@simnang.com"
}

Bank Card Update

Sends a request when a borrower credit/debit card is updated in Secure Payments.

{
"message": "A credit card was updated under the Secure Payments account pciwalletaccount@simnang.com"
}

User Password Update

Sends a request when the user password associated with a Secure Payments account is updated.

{
"message": "Secure Payments password for pciwalletaccount@simnang.com have been updated."
}

Payment Processing

Sends a request when a payment is processed in Secure Payments.

{
"type": "Authorize.net",
"processor": 1454,
"transaction-id": 6486581
}

Processor Create

Sends a request when a new processor is created in Secure Payments.

{
"type": "Authorize.net",
"id": 1739
}

Processor Delete

Sends a request when an existing processor is deleted from Secure Payments.

{
"type": "Authorize.net",
"id": "1740"
}

Processor Update

Sends a request when an existing processor is updated in Secure Payments.

{
"type": "Authorize.net",
"id": "1741"
}

User Settings Update

Sends a request when user settings are updated in Secure Payments.

{
"message": "Secure Payments settings for pciwalletaccount@simnang.com have been updated."
}


How did we do?


Powered by HelpDocs (opens in a new tab)