Secure Electronic Payments API

Signature capture can be accomplished by using the ArgoFire OCX control or this Web service hosted on the payment server. The URL to access this Web service is:

https://secure.ftipgw.com/ArgoFire/transact.asmx?op=ProcessSignature

Descriptions of the parameters are listed below.

The following tables contain sample data you can use for this Web service. The UserName, Password, and PNRef parameters should be changed when testing this example yourself. If a transaction already has an image, then the Web service will return “Original Transaction Already Has Receipt.”

Example: Sign and Associate
The example data below will draw a little square on the receipt and associate the receipt with the transaction with reference number 9568.

Response

Example: Create Receipt Image from File
It is possible to send a receipt image file through the ProcessSignature web service operation from a client-side application in order to associate it with a transaction. Due to the overall complexity of creating a receipt image with ProcessSignature, here is a general list of steps your client-side application would need to perform in order to send images to the Payment Server.

1. Get image file from hardware device, etc

2. Convert image format from hardware device to the TIFF image format, if it isn’t already in that format.

3. It is required that at this point you perform an LZW compression on the image data in the TIFF format to reduce the file size because the Payment Server will only accept image data up to 25KB. Here’s some general information about LZW compression for TIFF images

Compresses and decompresses without information loss, achieving compression ratios up to 5:1. It may be somewhat slower to compress and decompress than the PackBits scheme. 

4. At this point, it is required to compress the file itself with Zip compression to reduce the file size. Any PKZip-compatible Zip compressor and decompressor will work. IPWorks (www.ipworks.com) is a third-party provider of software tools and they have a product called “IPWorks! Zip” that can simplify the programmatic compression because it implements a PKZip-compatible Zip compressor and decompressor: the most common compression used on Windows Platforms

5. Base64 encode the image. This ensures that the binary-based information transported can be converted properly into text-based characters to send in the SignatureData parameter of ProcessSignature

6. Input the compressed/base64 encoded image data into the SignatureData parameter of ProcessSignature, and send it to the Payment Server

The example data below will save a receipt image to the Payment Server and associate the receipt with the transaction with reference number 3.

Response

The example data below will save a check image to the Payment Server and associate it with the transaction with reference number 5454

Response