Prompt for Signature Capture

Table of Contents 

1. Overview
2. Manual vs Digital Signature Capture
3. Request Signature

Overview

Customer-Present Cloud empowers integrators to enhance payment requests by prompting customers for additional information or actions using the payment device. Signature capture is a vital prompt, enabling integrations to request customer signatures when necessary.

This article provides insights into leveraging POI Device Prompts to facilitate signature capture during transactions.

Additional note: This feature applies primarily to magstripe transactions as signature capture enforcement for EMV transactions is typically controlled by the card's EMV chip and may not be overwritten.

Manual vs Digital Signature Capture

Signature capture methods vary based on the payment device used during the transaction. Some devices support digital signature capture directly on the device, while others require manual signatures off the device. Here's a breakdown:

Request Signature

To prompt the payment device for signature capture, integrations utilize the poi_prompt_signature parameter. This parameter accepts boolean values (true or false), with true prompting signature capture for the transaction.

Using the poi_prompt_signature parameter, here is an example of how a Customer-Present Cloud request should be formatted for submission when requesting signature capture:

POST: /api/transact.php
PARAMS:
[ 
    security_key : your_security_key 
    poi_device_id : "POI Device ID Here"
    type : sale
    amount : 10.00
    response_method : asynchronous 
    poi_propmt_signature: true
]

The above example will charge the end customer 10.00 and prompt the customer to submit a signature in order to complete the transaction. Once the customer provides the signature, the transaction will continue and be completed. Should no signature be provided on the device the transaction will remain stuck and eventually timeout.