triPOS^®

Signature Prompt

The following triPOS endpoints accept a new promptForSignature field in the configuration section of the request. This new field allows you to tell triPOS on a per-request basis how the PIN pad should prompt for a signature.

• POST /api/v1/sale
• POST /api/v1/refund
• POST /api/v1/return/{transactionId}/{paymentType}
• POST /api/v1/authorization
• POST /api/v1/authorization/{transactionId}/completion
• POST /api/v1/force/credit

The following conditions apply to this new field:

• If the promptForSignature field is not supplied, the signature capture will be handled as it was prior to this addition.
• The promptForSignature field affects credit MSR and all EMV transactions.
• If triPOS would normally require a signature for a transaction and you specify a promptForSignature value of Never, you will receive a new statusCode of SignatureRequiredButPromptSuppressedByMerchant in the signature section.

The promptForSignature field takes one of the following three values:

• UseThreshold - Tells triPOS to use the thresholdAmount field in the configuration section, if provided, to determine whether to prompt for a signature. Otherwise, use the creditSaleSignatureThresholdAmount in the triPOS.config. This option is only available for the POST /api/v1/sale endpoint.
• Always - Tells triPOS to prompt for a signature for the request.
• Never - Tells triPOS to skip prompting for a signature for the request.