Visit our Secure Web Pay section at:
Secure Web Pay Charge Template allows you to host a payment page on Payments Gateway servers that has pre-defined data elements included. It also supports a credit card swiper and customization of the form.
The Secure Web Pay Charge template API supports these operations:
For a list of Type Definitions click here.
1 = Saves payment method
2 = Saves client and payment method
Blank = Niether payment method or client is saved.
Look and Feel
"yes" or "no"
yes = "Addtional Transaction" button will show on the confirm page.
Blank = no
1 = 8.5 2 = 3"
This field is ignored if ReturnURL <> null
* Pass in Allowed = if the parameter is passed in with the request, the corresponding data element on the form is replaced with the passed-in text.
A receipt can be generated in either a 8 1/2 x 11 PDF or 3 inch format.
Certain form fields are required depending on the type of transaction being performed.
Authentication is done using a HMAC-MD5 hash that includes the following fields.
pg_ts_hash = HMACMD5(pg_api_login_id + "|" + pg_transaction_type + "|" + pg_version_number + "|" + pg_total_amount + "|" + pg_utc_time + "|" + pg_transaction_order_number, pg_secure_transaction_key)
pg_ts_hash_response = HMACMD5(APILoginID + "|" + pg_trace_number + "|" + pg_total_amount + "|" + pg_utc_time , pg_secure_transaction_key)
The API Login ID and Secure Transaction Key can be found in the Virtual Terminal under Gateway Settings.
Secure Web Pay Charge allows different templates to be used depending on the value passed for the parameter pg_template_id.
Template #1 (cc shown)
Template #2, #3 (cc shown)
Note: Postal code is not required when using template #3.
UTC Time Expired + or -5 min
Return URL not valid
Sales tax amount not valid