Secure Payments API – LoanPaymentPro Processor

Introduction

LoanPaymentPro is unique among Secure Payments (formerly PCI Wallet) processors. This is because it supports both eCheck and Credit Card transactions. This article solely explains how to use the API to create LoanPaymentPro processors in Secure Payments. For more information on using the API to process LoanPaymentPro payments, check out the articles listed below.

How To

To create a LoanPaymentPro processor, send a POST request to the endpoint:

POST https://pciwallet.simnang.com/api/processors/loanpaymentpro

Sample payload:

{
"loanpaymentpro": {
"name": "test123",
"transaction_key": "string",
"tx_verification": true,
"type": "ach"
}
}

  • name - The name of the LPP processor you are created. This name must be unique.
  • transaction_key - The key for what type of transaction the processor is using. Use 7bfb847f-60ce-44b9-8037-7a63f1b4bfb1 for ach transactions; use 744111ee-b0f3-4016-87ba-7a46335a32a5 for credit card transactions.
  • tx_verification - Determines if two-step verification for payments is enabled. Users will be charged twice when this option is set to "true" since the user is charged for a preliminary authorization transaction and then also for processing the actual payment.
  • type - Determines whether the processor will run credit cards (credit-cards) or e-checks (ach).

Sample cURL payload:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'authorization: YOUR AUTH' --header 'secret: YOUR SECRET' -d '{ \
"loanpaymentpro": { \
"name": "sample processor", \
"transaction_key": YOUR TRANSACTION KEY, \
"tx_verification": true, \
"type": "credit-card" \
} \
}' 'https://pciwallet.simnang.com/api/processors/loanpaymentpro'

Notice that the request to create a LoanPaymentPro processor contains a type attribute. This is used to indicate what type of transactions you intend to process with this particular processor. Set the type to “ach” to process eCheck transactions and “credit-card” to process credit card transactions.

Response:

{
"id": 1
}

After a processor is created, working on transactions will use different paths depending on transaction types. Credit card transactions will use loanpaymentpro-credit-card and eCheck transactions will be on the path loanpaymentpro-ach.


How did we do?


Powered by HelpDocs (opens in a new tab)