Separate Debit Processing Controls (iPOSTransact API)

Separate Debit Processing Controls (iPOSTransact API)

Merchants can now configure PIN Debit and Signature Debit behavior separately under the existing “Treat Debit as Cash” functionality in the Portal. This enhancement provides greater flexibility by allowing fees to be applied or removed independently based on how the debit transaction is processed in iPOSTransact API flows.

  • Supported Channels: iPOSTransact API (Sale, Ticket)

What’s New

Two parameters are available under Dual Pricing to control debit behavior:

  • PIN Debit – Controls fee application for debit transactions authenticated using a PIN
  • Signature Debit – Controls fee application for debit transactions processed without a PIN

Behavior

ConditionResult
PIN Debit is enabledFee is removed (treated as cash)
PIN Debit is disabledA fee is applied
Signature Debit is enabledFee is removed
Signature Debit is disabledFee is applied
Treat Debit as Cash is disabledA fee is applied for all transactions
Credit card transactionsThe fee is always applied

Where to Configure

  • Log in to the iPOSpays portal using an ISO account
  • Navigate to: S.T.E.A.M → Search and select TPN → Edit Parameters
  • Go to Fee Settings → Dual Pricing
  • Locate the following parameters:
    • PIN Debit
    • Signature Debit
  • Enable or disable each option based on the required behavior
  • Click Save

Additional Behavior (iPOSTransact API)

  • If the transaction is processed as PIN-authenticated Debit → PIN Debit logic is applied
  • If the transaction is processed as non-PIN (Signature) Debit → Signature Debit logic is applied
  • The system determines the debit type based on transaction processing and switch response

  • Both PIN Debit and Signature Debit work independently
  • Behavior depends on how the transaction is processed (PIN vs non-PIN)
  • Backward compatibility is maintained
  • If parameters are not configured, the system follows the existing Treat Debit as Cash behavior

Developer Documentation

For complete API details, including request and response structures, refer to: