PINless Bill Pay - pldbillpay

Merchants that process both recurring transactions and PINless debit transactions can take advantage of PINless bill pay. PINless bill pay transactions can run after confirming that the card the transaction will charge to is valid using binlookup.


PINless bill pay is available on terminals with the following settings:

  • Region set to USA
  • Debit enabled
  • PINless Debit Bill Pay enabled
  • Eligible Merchant MCC/SIC Code

Process Flow

Before sending a request for a PINless bill pay transaction, you need to confirm that the card supports PINless bill pay as an option. To do this, send a binlookup request and check for the following field/value combinations.

  • <debit>Y</debit>
  • <billPaymentSupport>Y</billPaymentSupport>


15 | numeric | required
Merchant ID
Elavon-assigned Converge account ID.
15 | alphanumeric | required
Converge User ID
The user ID with Hosted Payment API User status that can send transaction requests through the terminal.
64 | alphanumeric | required
Terminal ID
Unique identifier of the terminal that will process the transaction request and submit to the Converge gateway.
Important: The ssl_user_id sending the transaction request must be associated with the terminal that will process the request.
20 | alphanumeric | required
Transaction Type
Value: pldbillpay
11 | numeric | required
Transaction Amount
The base amount that does not include the Surcharge amount.
Format: Number with 2 decimals places
25 | numeric | required
Customer/Payee Account Number
[Card Data]
18 | numeric | required
Card Number
Card Number as it appears on the debit card.
4 | numeric | optional
Card's Expiry Date
Date when the card becomes invalid.
Format: MMYY
1 | numeric | required
Bank Deposit Account Type
Valid values:
  • 0 - Checking
  • 1 - Saving


Transaction Outcome
An ssl_result = 0 indicates an approved transaction.
An ssl_result not equal to 0 indicates a declined and unauthorized transaction.
Transaction Result Message
Refer to the Debit Card Response Codes section for an extensive list of possible returned messages.
Transaction ID
Unique identifier of the transaction.
Processing Date and Time
Indicates when Converge processed the transaction.
Format: MM/DD/YYYY hh:mm:ss AM/PM
Example: 03/18/2010 10:34:10 AM
Transaction Approval Code
Unique code returned by the credit card processor that indicates the approval status of the transaction.
Masked Card Number
Converge only returns the first 2 or last 4 digits of the regular PAN.
Bank Deposit Account Type
Valid values:
  • 0 - Checking
  • 1 - Saving
Transaction Amount
The total transaction amount that may include the Surcharge amount.
Customer/Payee Account Number
Returned only if an error occurs. Refer to the Error Codes section for more information.
Error Code
Typically, when the transaction failed validation or the request is incorrect. This will prevent the transaction from going to authorization. This is a numeric field.
Error Message
Detailed explanation of the error. This field may be changed based on merchant configuration in the user interface.
Error Name
Error name or reason for the error.

Sample Code




Successful Response

    <ssl_txn_time>02/05/2020 01:03:56 PM</ssl_txn_time>

Card Not Eligible

    <errorName>Payment Card Not Eligible for Debit Bill Pay</errorName>
    <errorMessage>The provided payment card is not eligible for Debit Bill Pay.</errorMessage>

PINless Bill Pay Not Enabled

    <errorName>This terminal or user id is not permitted to process this transaction type.</errorName>
    <errorMessage>Not Permitted</errorMessage>