ArgoFire Gateway
| ProcessSignature | ![]() |
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.
| Parameter | Description |
| UserName | Required. User name assigned in the payment server |
| Password | Required. Password for the user name assigned in the payment server |
| SignatureType | Required. The type of signature to capture. Valid values are:
|
| SignatureData | Required. If the SignatureType is set to Signature4, a string value of vector
coordinates delimited with a ^ character in the following format: x1,y1^x2,y2^xN,yN^~ If there is a pen-up event, then you use the coordinate 0,65535 to signal a break in the line ^ is the coordinate delimiter, ~ is the ending delimiter, and a comma (,) is the vector delimiter If the SignatureType is set to Receipt1, then you must compress and Base64 encode the image data. See the examples section below for more information |
| PNRef | Required. The unique payment reference number assigned to the transaction |
| Result | Optional. An indicator that specifies if the processed transaction was approved |
| AuthCode | Optional. The authorization code from the authorization of a transaction |
| ExtData | Optional. Extended data in XML format. Valid values are:
|
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.”
Examples
ArgoFire Gateway SDK - Main |
Glossary of Terms |
Response Codes |
|
![]() |
|||

