Secure Payments Events

General

Secure Payments (formerly PCI Wallet) will send information to a specified URL when certain events occur. If you are using Secure Paymentst with LoanPro, we will provide some of the URLs to make your Secure Payments integration full-featured. Secure Payments events include:

  • Bank Account Create
  • Bank Account Delete
  • Bank Account Update
  • Bank Card Create
  • Bank Card Delete
  • Bank Card Update
  • Nacha Batch Generation - LoanPro Callback URL: https://loanpro.simnang.com/api/public/thirdparty.php/pciw/nacha-batch-generation/callback
  • NACHA File Generation - LoanPro Callback URL: https://loanpro.simnang.com/api/public/thirdparty.php/pciw/nacha-file-generation/callback
  • User Password Update
  • Payment Processing
  • Processor Create
  • Processor Delete
  • Processor Update
  • User Settings Update
  • Transaction Status Update - LoanPro Callback URL: https://loanpro.simnang.com/api/public/thirdparty.php/pciw/transaction-updated/callback
    • Note: If the payment is reversed, the r-code is included in the transaction status update callback.

You can add up to 5 callback URLs per event. To turn on events or update event URLs, navigate to Events inside Secure Payments.

Use the toggle switches to the right of an event to turn it on or off. Click None or the listed URL to add or update the callback URL for an event.

To add an event, click .

Choose the event type for which you want to add a URL from the Event type drop-down. Enter the URL in the URL field. Click .

NACHA Batch Generation

If you add the LoanPro callback URL for NACHA file generation, https://loanpro.simnang.com/api/public/thirdparty.php/pciw/nacha-batch-generation/callback, LoanPro will get updated with NACHA batch IDs, assigned by Secure Payments for transactions processed with a  NACHA processor. This will let you pull payments based on their batch ID.

NACHA File Generation

If you add the LoanPro callback URL for NACHA batch generation, https://loanpro.simnang.com/api/public/thirdparty.php/pciw/nacha-file-generation/callback, LoanPro will get updated when a NACHA file is generated.

Transaction Status

Including the LoanPro URL for transaction status updates, https://loanpro.simnang.com/api/public/thirdparty.php/pciw/transaction-updated/callback, payments will get updated with the transaction status from Secure Payments as they move through the payment process.

Other Events

  • Bank Account Create - Sends a request when a new borrower bank account is created in Secure Payments.
    • Example:
      {
      "type": "checking"
      }
  • Bank Account Delete - Sends a request when a borrower bank account is deleted in Secure Payments.
    • Example:
      {
      "message": "A bank account has been deleted under the PCI-Wallet account pciwalletaccount@simnang.com"
      }
  • Bank Account Update - Sends a request when a borrower bank account is updated in Secure Payments.
    • Example:
      {
      "message": "A bank account has been updated under the PCI-Wallet account pciwalletaccount@simnang.com"
      }
  • Bank Card Create - Sends a request when a new borrower credit/debit card is added in Secure Payments.
    • Example:
      {
      "message": "A credit card was added under the PCI-Wallet account pciwalletaccount@simnang.com"
      }
  • Bank Card Delete - Sends a request when a borrower credit/debit card is deleted in Secure Payments.
    • Example:
      {
      "message": "A credit card was deleted under the PCI-Wallet account pciwalletaccount@simnang.com"
      }
  • Bank Card Update - Sends a request when a borrower credit/debit card is updated in Secure Payments.
    • Example:
      {
      "message": "A credit card was updated under the PCI-Wallet account pciwalletaccount@simnang.com"
      }
  • User Password Update - Sends a request when the user password associated with a Secure Payments account is updated.
    • Example:
      {
      "message": "PCI-Wallet password for pciwalletaccount@simnang.com have been updated."
      }
  • Payment Processing - Sends a request when a payment is processed in Secure Payments.
    • Example:
      {
      "type": "Authorize.net",
      "processor": 1454,
      "transaction-id": 6486581
      }
  • Processor Create - Sends a request when a new processor is created in Secure Payments.
    • Example:
      {
      "type": "Authorize.net",
      "id": 1739
      }
  • Processor Delete - Sends a request when an existing processor is deleted from Secure Payments.
    • Example:
      {
      "type": "Authorize.net",
      "id": "1740"
      }
  • Processor Update - Sends a request when an existing processor is updated in Secure Payments.
    • Example:
      {
      "type": "Authorize.net",
      "id": "1741"
      }
  • User Settings Update - 
    • Example:
      {
      "message": "PCI-Wallet settings for pciwalletaccount@simnang.com have been updated."
      }


How did we do?


Powered by HelpDocs (opens in a new tab)