{"info":{"_postman_id":"d35b6b64-a9ee-47de-aa96-bec95e0d235a","name":"Paygistix Web - SDK v 1 03","description":"

About This Guide

Intended Audience

This guide is intended for software developers and product integrators who are looking to perform simple payment integrations using Payment Logistics; Paygistix Web hosted payment portal through Buttons, Forms and Custom integration.

Prerequisites

Integrators should have a basic understanding of HTML.

To use some of the more advanced features including security hash value generation, knowledge of server side website development is required.

Please contact Payment Logistics support if you require further information.

Configuring Your Account

Login to the Paygistix Web Administration Portal

Following a successful login you should see the following page.

Configuring Options

Choose Account Profile, from the portal menu.

This is the main configuration screen for the merchant. Complete the options as required.

Username

The username used to login to the admin portal, also used to identify the correct account at code level from Buttons, Forms and Custom integrations.

Password

The password used to login to the admin portal. This password should be kept safe and must not be sent in Button, Forms or Custom integrations client side code.

Direct Gateway Authentication

With this option selected, the above username and password are authenticated directly against the Payment Logistics payment gateway and used for processing transactions.

Gateway Username

Username issued for access to the Payment Logistics payment gateway. Not available when \"Direct Gateway Authentication\" is selected.

Gateway Password

Password issued by Payment Logistics. Not available when \"Direct Gateway Authentication\" is selected.

Gateway Vendor ID

Vendor ID issued by Payment Logistics. Not required when \"Direct Gateway Authentication\" is selected as this is set automatically.

Secret Hash Key

This hash key is used to create a secure token that can be passed to and from the originating website and the Paygistix Web service. See the section later on for more details regarding how to use this. This is automatically handled by the Form and Button generators.

Cards Accepted

Choose which cards you wish to accept on the payment screen.

Merchant Name

Name that is displayed on payment screens.

Email Address

Email address to which successful payment confirmations and order information will be sent.

Enable Postback

If this box is checked then a server side postback will be initiated on completion of a successful transaction notifying your website of the order details including amount, billing/shipping details etc.

Postback URL:

The URL of the server side page to be called on successful completion of an order. The order values will be posted to this URL using an HTTP POST. See Section 5.2 for more details.

Use HTTP Get Rather than POST

When this option is selected parameters will be sent to the postbacks using the GET method, i.e. appended to the URL. The standard and default method for postbacks is to use a HTTP POST where name value pairs are sent in the body of the request rather than as parameters to the URL.

Additional Options

Set additional flags regarding the payment process as follows.

Billing Dropdown

Determines which geographies are supported, US only, US & Canada, Whole World.

Capture Shipping Address

Fields allowing the customer to enter a different shipping address from the billing address provided during the checkout process.

CV2/CVV Mandatory

The three digits on the back of a card (four on the front for AMEX) required when accepting payments becomes mandatory when checked.

Capture Email Address During Process

When enabled customer will be prompted to enter an email address during the transaction process.

Customer Email Acknowledgement

Sends a customer an order acknowledgment email on completion of a transaction.

Merchant Email Acknowledgement

Sends the merchant an order acknowledgment email on completion of a transaction.

Terms & Conditions must be accepted

Requires a user to check the box next to terms and conditions before continuing with the transaction.

Transparent Redirect: allows capture of credit card details in your own web form which then get passed to Paygistix Web for processing. No user interface is required, with the results being posted directly back to your own web form on completion of the transaction. If this option is selected Inbound HashMandatory: will also be automatically selected.
Inbound Hash Mandatory: with this option selected, the calling script must pass a valid HASH value when initiating the payment page. See Section 5.1 on generating Hash values.

Return URL Parameter Passing Method

When the transaction is complete and if a ReturnURL has been supplied when initiated from the calling web page, this option determines how certain parameters will be passed via a HTTP GET back to the site. There are three possible choices.

No parameters return. The ReturnURL will be loaded, but no details of the order will be passed.
Details of the transaction will be appended to the ReturnURL following a ?. i.e. using a standard HTTP GET.
Details of the transaction will be appended to the ReturnURL via a fragment identifier (i.e. following a #). This occurs on the client side only, data is not sent across the Internet and javascript must be used on the destination page to access the fragment. http://en.wikipedia.org/wiki/Fragment_identifier

Return on Error and Success States

Typically when processing a credit card charge, the user has an option to retry a transaction, potentially with new card, in the event their initial attempt declines. If the \"Return on Error and Success\" option is set the system will immediately load the ReturnURL even on a failed card transaction allowing the host application to respond to the error directly. This option is set at account level. If you wish to only use this option on certain requests the same thing can be achieved by sending in OPTIONS=RETURNONERROR in the calling form.

Custom Logo

Allow the merchant to upload a specific header graphic that will replace the generic Payment Logistics logo. The graphic must be either a JPG file or PNG file no bigger than 200px wide x 100px high and no larger than 30k in size.

Terms & Conditions Text

This is the merchant configurable text to show on the popup Terms & Conditions window if Terms & Conditions are enforced.

U.S. Applicable Tax Rates

Use this screen to set the relevant state taxes depending on where the merchant is located. Tax will automatically be calculated and added to transactions when a customer from a matching state visits the payment page.

Generating Simple Buttons & Forms

Generate Button Code

The button generator allows you to create simple template code that can easily be pasted into an existing website. The generator builds a unique button using the HTML form code required which is then ready for immediate use.

Button Text

This is the word that will appear on the button when placed on a page. It can be any text you wish i.e. \"Pay Now\" , \"Buy Online\" or \"Donate\".

Value Range

To make the button a specific value such as $10 set both boxes to 10. You can also provide a range of values (perhaps for a donation). i.e. between 10 and 100. The maximum value in the range is $99,999.

Return URL

This is the page the user will be returned to once they have completed their purchase. Some order details will also be passed back to the page to allow for certain scripting to take place. See Section 5.3 for more information.

Example code generated by the Button Generator:

\n \n

<form action=\"https://safepaycert.paymentlogistics.net/step1.asp\" method=\"post\">\n<input type=\"hidden\" name=\"txnType\" value=\"button\" />\n<input type=\"hidden\" name=\"description\" value=\"Donate $100\" />\n<input type=\"hidden\" name=\"amountLow\" value=\"100\" />\n<input type=\"hidden\" name=\"amountHigh\" value=\"100\" />\n<input type=\"hidden\" name=\"merchantID\" value=\"test1\" />\n<input type=\"hidden\" name=\"buttonID\" value=\"09032011190755\" />\n<input type=\"hidden\" name=\"hash\" value=\"62ea3cd4d607a132a7d8d250e42d3574\" />\n<input type=\"hidden\" name=\"ReturnURL\" value=\"https://safepaycert.paymentlogistix.net/testreturn.asp\" />\n<input type=\"submit\" name=\"submit\" value=\"Donate $100\" />\n</form>\n

The above code includes a standard Input button which can be further styled with CSS to match your website. When pasted to a webpage the button will show as follows:

Pressing the button takes you to the payment page where the amount is already selected.

Form Generator

The form generator allows you to create simple template code that can easily be pasted into an existing website. The generator builds the HTML form code which is ready for immediate use however some basic html customization can be done to change the look and feel of the form. The form generator takes care of scripting the secure token based on the Secret Hash Key and other data so major changes to the code outside of the form generator such as adding additional products, will cause an invalid hashing error. If your order form contains many items and you constantly need to add or subtract items from it, we recommend a custom integration though we are in the process of adding the ability to reload a product form in the Form Generator for simple modification.

Product lines (multiple rows)

Code, Description & Price

You can add as many products as you like. Each line will take a product code, something to identify the product with when the order comes through, a short one line description and a product price.

Return URL

This is the page the user will be returned to once they have completed their purchase. Some order details will also be passed back to the page for allowing for certain scripting to take place. See the section later in this guide regarding \"Return URL format\"

Transaction Type

You can chose whether you wish the transaction to be an AUTH only or a SALE. If you post an AUTH only you will need to use a FORCE transaction later to force the transaction into the batch.

Capture Fields

You can give an optional list of fields if you want to capture some additional simple information during the transaction process. Perhaps you might wish to as for a date or birth or gender. Simply enter Date Of Birth, Gender in this box and those optional fields will be displayed. If you want to make one of these capture fields mandatory simply append an * to the field name, e.g: Date Of Birth *, Gender

The code generated includes a simple javascript calculator that adds up the selected products quantities and multiplies these by each price to give a guide total price prior to visiting the payment screen. Example code produced by Form Generator:

\n \n

<form action=\"https://safepaycert.paymentlogistics.net/step1.asp\" method=\"post\">\n<style type=\"text/css\">\n  .pxPrice {text-align:right;}\n  .pxQty {width:60px;text-align:right;}\n</style>\n<table id=pxForm name=pxForm>\n  <thead>\n    <th>Code</th><th>Item</th><th>Price</th><th>Qty</th>\n  </thead>\n  <tbody>\n    <tr>\n      <td class=\"pxCode\">\n         001-A-RED<input type=\"hidden\" name=\"pxCode1\" value=\"001-A-RED\" />\n      </td>\n      <td class=\"pxDescription\">\n         Ladies shoe - Red<input type=\"hidden\" name=\"pxDescription1\" value=\"Ladies shoe - Red\" />\n      </td>\n      <td class=\"pxPrice\">\n          $39.00<input type=\"hidden\" name=\"pxPrice1\" id=\"pxPrice1\" value=\"39.00\" />\n      </td>\n      <td>\n          <input type=\"text\" class=\"pxQty\" name=\"pxQty1\" id=\"pxQty1\" value=\"0\" onblur=\"javascript:formatQty(this);\" maxlength=\"3\"/>\n      </td>\n    </tr>\n    <tr>\n      <td class=\"pxCode\">\n         001-B-BLACK<input type=\"hidden\" name=\"pxCode2\" value=\"001-B-BLACK\" />\n      </td>\n      <td class=\"pxDescription\">\n         Ladies shoe - Black<input type=\"hidden\" name=\"pxDescription2\" value=\"Ladies shoe - Black\" />\n      </td>\n      <td class=\"pxPrice\">\n          $29.00<input type=\"hidden\" name=\"pxPrice2\" id=\"pxPrice2\" value=\"29.00\" />\n      </td>\n      <td>\n          <input type=\"text\" class=\"pxQty\" name=\"pxQty2\" id=\"pxQty2\" value=\"0\" onblur=\"javascript:formatQty(this);\" maxlength=\"3\"/>\n      </td>\n    </tr>\n    <tr>\n      <td class=\"pxCode\">\n         001-C-SILVER<input type=\"hidden\" name=\"pxCode3\" value=\"001-C-SILVER\" />\n      </td>\n      <td class=\"pxDescription\">\n         Ladies shoe - Silver<input type=\"hidden\" name=\"pxDescription3\" value=\"Ladies shoe - Silver\" />\n      </td>\n      <td class=\"pxPrice\">\n          $39.00<input type=\"hidden\" name=\"pxPrice3\" id=\"pxPrice3\" value=\"39.00\" />\n      </td>\n      <td>\n          <input type=\"text\" class=\"pxQty\" name=\"pxQty3\" id=\"pxQty3\" value=\"0\" onblur=\"javascript:formatQty(this);\" maxlength=\"3\"/>\n      </td>\n    </tr>\n  </tbody>\n  <tfoot>\n    <tr>\n      <td colspan=4 align=right>\n         <span id=\"pxTotal\"><b>Total $0.00<b/> </span><input type=\"submit\" id=\"pxSubmit\" value=\"Pay Now\" />\n      </td>\n    </tr>\n  </tfoot>\n</table>\n<input type=\"hidden\" name=\"txnType\" value=\"form\" />\n<input type=\"hidden\" name=\"merchantID\" value=\"test1\" />\n<input type=\"hidden\" name=\"formID\" value=\"09032011192442\" />\n<input type=\"hidden\" name=\"hash\" value=\"80cd73d5b67cb238495f7d84500cef4c\" />\n<input type=\"hidden\" name=\"ReturnURL\" value=\"https://safepay.paymentlogistix.net/testreturn.asp\" />\n</form>\n<script src=\"https://safepaycert.paymentlogistics.net/form.js\" type=\"text/javascript\">\n</script>\n

The resulting form looks like this in a browser and can be easily styled with CSS:

.\n

\n \n

Hash Generation

Both when calling the payment gateway and receiving a postback you can use an MD5 hash value to validate that the call is authenticated.

We use a standard digest hashing algorithm called MD5 along with a secret shared key value on your profile to generate the MD5 prior to sending and receiving information between your site and ours.

In the case of the Button and Form generators the MD5 value is embedded automatically, this way if someone maliciously attempted to impersonate your site it would make it difficult for them to change the monetary values and details sent and received.

When coding your own integrations to the Paygistix Web service you will need to generate your own Hash value. Here is some example pseudo code:

\n \n

String InputValue = SharedSecretKey + MerchantID + Amount + OrderID\nString HashValue = MD5(InputValue)\n

Transparent Redirect (Only): When coding your own integrations to the Paygistix Web service you will need to generate your own Hash value. Here is some example pseudo code:

\n \n

String InputValue = SharedSecretKey + MerchantID + Amount \nString HashValue = MD5(InputValue)\n

There are many libraries and implementations for MD5 depending on what your programming language of choice is. Google \"MD5\" and your preferred Server Side Programming Language for more information or contact Payment Logistics for assistance.

Server Postback

As another level of security and validation you can configure the Payment process to post back a server to server message confirming when a transaction is complete. These messages can be picked up by your web server and used to changes the status of an order, or notify a customer that their order has been accepted.

Within the administrator console there is an option to enable the postback for all Buttons, Forms or Custom payment request. When a postback occurs the Paygistix Web service uses a HTTP POST and sends back value pairs such as the following to your server.

OrderID
Description

For a button or custom form this will be the Button Text or the Description that was sent in to the payment page.
For a Generated Form this will be a list of the items selected and their quantities. In the format ProductCode1=Qty1|ProductCode2=Qty2|ProductCode3=Qty3

Amount - The transaction total amount
TxnType - BUTTON, FORM, SALE or AUTH
PNRef - The unique transaction reference returned from the payment gateway
AuthCode - The AuthCode returned from the Credit Card process
Hash - The Hash Value returned is made up of the MD5 signature of the following concatenated fields

SharedPrivateKey
MerchantID
Amount
OrderID
PNRef

Message
Result
CardType
Last4
ExpDate
Name
Email
BillingAddress1
BillingAddress2
BillingCity
BillingState
BillingZIP
BillingCountry
ShippingAddress1
ShippingAddress2
ShippingCity
ShippingState
ShippingZIP
ShippingCountry

\n\n

Return URLs

On successful completion of a transaction, the website will return to a predefined URL passed in via the calling form.

The following parameters will be available (depending on the function called)

MerchantID
Amount
OrderID
PNRef
Result
TxnType
Hash - The hash is made up from the MD5 signature of the following concatenated fields

Shared Secret Key
The ReturnURL sent in to the payment page
MerchantID
Amount (If relevant)
OrderID (If relevant)
PNRef

\n\n\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"About This Guide","slug":"about-this-guide"},{"content":"Configuring Your Account","slug":"configuring-your-account"},{"content":"Generating Simple Buttons & Forms","slug":"generating-simple-buttons-forms"},{"content":"Hash Generation","slug":"hash-generation"},{"content":"Server Postback","slug":"server-postback"},{"content":"Return URLs","slug":"return-urls"}],"owner":"9571363","collectionId":"d35b6b64-a9ee-47de-aa96-bec95e0d235a","publishedId":"TWDfDsrM","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"ededed","highlight":"006fba"},"publishDate":"2022-02-11T19:07:30.000Z"},"item":[{"name":"SDK – More Advanced Custom Forms","item":[{"name":"SALE ","id":"f7415689-c0cb-44b5-96b4-97c2100bb6a5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*This can be set to either SALE or AUTH (required)

\n","key":"TxnType","type":"text","value":"SALE"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*A unique alphanumeric reference that you can use to identify an individual order

\n","key":"OrderID","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"Amount","type":"text","value":""},{"description":"

*This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:\nSharedSecretKey (found in the profile page of the portal)\nMerchantID \nAmount (Format as 0000.00)\nOrderID\n(required)\nSee the next section regarding generation of Hash values.

\n","key":"Hash","type":"text","value":""},{"description":"

The page to load once the payment process is complete.

\n","key":"ReturnURL","type":"text","value":""},{"description":"

The page to return to should the customer quit the transaction before completion

\n","key":"CancelURL","type":"text","value":""},{"description":"

A text description for the item being purchased

\n","key":"Description","type":"text","value":""},{"description":"

When passed NOADDRESS will skip requesting a credit card address\nWhen passed RETURNONERROR the ReturnURL will be immediately loaded even if the transaction fails or is declined.

\n","key":"Options","type":"text","value":""},{"description":"

When this parameter is supplied the ability to enter a loyalty card number and optional PIN will be enabled during the sales process. The loyalty parameter requires a value type and optional promotion code for a specific loyalty program separated by a colon if both are supplied. Examples could be: \nPoints - The default value type for loyalty\nPunches - GoLarge – Stores against the Punches value type under the promotion GoLarge

\n","key":"Loyalty","type":"text","value":""},{"description":"

The ratio of loyalty points issued to dollars spent. For instance, if value is 100 then 100 points will be issued for each dollar of transaction.

\n","key":"LoyaltyRatePerUnit","type":"text","value":""},{"description":"

Comprised of the following fields:\nCardName\nEmail\nBillingAddress1\nBillingAddress2\nBillingCity\nBillingState\nBillingZIP\n*If any part of the Billing address is sent through, then BillingAddress1, BillingCity, BillingState and BillingZIP must be supplied.

\n","key":"Billing Address","type":"text","value":""},{"description":"

Comprised of the following fields:\nShippingAddress1\nShippingAddress2\nShippingCity\nShippingState\nShippingZIP

*If any part of the Shipping address is sent through, then ShippingAddress1, ShippingCity, ShippingState and ShippingZIP must be supplied.

\n","key":"Shipping Address","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

Post a SALE against a particular card. This transaction type is identical to an AUTH except that an authorization needs to be subsequently forced into the batch using the FORCE command.

Transaction Request, Form Action & Method:

For SALE the calling form should be set to use the POST method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp

\n\n

e.g. <form action=\"https://safepaycert.paymentlogistics.net/transaction.asp\" method=\"post\">\n\n

Mandatory Parameters

TxnType: This can be set to either SALE or AUTH

MerchantID: This needs to be set to the account Username used to login to the portal

OrderID: A unique alphanumeric reference that you can use to identify an individual order

Amount: The amount of the transaction not including the currency symbol. (As 0000.00)

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
MerchantID
Amount (Format as 0000.00)
OrderID

See the next section regarding generation of Hash values.

Optional Parameters

ReturnURL: The page to load once the payment process is complete.

CancelURL: The page to return to should the customer quit the transaction before completion

Description: A text description for the item being purchased

Options: When passed NOADDRESS will skip requesting a credit card address

When passed RETURNONERROR the ReturnURL will be immediately loaded even if the transaction fails or is declined.

Loyalty: When thisparameter is supplied the ability to enter a loyalty card number and optional PIN will be enabled during the sales process. The loyalty parameter requires a value type and optional promotion code for a specific loyalty program separated by a colon if both are supplied. Examples could be:

Points - The default value type for loyalty
Punches - GoLarge - Stores against the Punches value type under the promotion GoLarge

Contact us regarding our loyalty programs if you would like these features enabled on your account.

LoyaltyRatePerUnit: The ratio of loyalty points issued to dollars spent. For instance, if the value is 100 then 100 points will be issued for each dollar of transaction.

Billing Address: Comprised of the following fields:

CardName
Email
BillingAddress1
BillingAddress2
BillingCity
BillingState
BillingZIP

If any part of the Billing address is sent through, then BillingAddress1, BillingCity, BillingState and BillingZIP must be supplied.

Shipping Address: Comprised of the following fields:

ShippingAddress1
ShippingAddress2
ShippingCity
ShippingState
ShippingZIP

If any part of the Shipping address is sent through, then ShippingAddress1, ShippingCity, ShippingState and ShippingZIP must be supplied.

Transaction Response

Following a successful transaction the following 3 events will occur:

An email will be received at the profile email address notifying that an order has been raised.
The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
OrderID: The order reference supplied
Amount: The amount of the transaction
PNRef: The Transaction reference (used for FORCE, VOID, CREDIT etc)
Result: The status of the transaction, 0 for success
TxnType: Either SALE or AUTH in this instance
Last4: The last 4 digits of the card
CardType: The type of card processed (Mastercard, Visa etc)

The following fields will be posted back to your receiving form if (enabled in the profile)

OrderID: The order reference supplied
Description: The product / order description
Amount: The amount of the transaction
TxnType: Either SALE or AUTH in this instance
Hash
BillingFirstName, BillingLastName, BillingEmail, BillingAddress1, BillingAddress2, BillingCity, BillingState, BillingZIP
ShippingAddress1, ShippingAddress2, ShippingCity, ShippingState, ShippingZIP
PNRef: The Transaction reference (used for FORCE, VOID, CREDIT etc)
AuthCode: The credit card authorization code
Last4: The last 4 digits of the card
CardType: The type of card processed (Mastercard, Visa etc)

The Hash value returned in the Postback URL is made up of the following values. (See Section 5.1 for further details)

SharedSecretKey
MerchantID
Amount
OrderID
PNRef

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
Amount,
OrderID,
PNRef

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"f7415689-c0cb-44b5-96b4-97c2100bb6a5"},{"name":"AUTH","id":"f19386c0-d74d-427c-8db7-2e67e248bcfa","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*This can be set to either SALE or AUTH (required)

\n","key":"TxnType","type":"text","value":"AUTH"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*A unique alphanumeric reference that you can use to identify an individual order

\n","key":"OrderID","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"Amount","type":"text","value":""},{"description":"

\n","key":"Hash","type":"text","value":""},{"description":"

The page to load once the payment process is complete.

\n","key":"ReturnURL","type":"text","value":""},{"description":"

The page to return to should the customer quit the transaction before completion

\n","key":"CancelURL","type":"text","value":""},{"description":"

A text description for the item being purchased

\n","key":"Description","type":"text","value":""},{"description":"

When passed NOADDRESS will skip requesting a credit card address\nWhen passed RETURNONERROR the ReturnURL will be immediately loaded even if the transaction fails or is declined.

\n","key":"Options","type":"text","value":""},{"description":"

\n","key":"Loyalty","type":"text","value":""},{"description":"

The ratio of loyalty points issued to dollars spent. For instance, if value is 100 then 100 points will be issued for each dollar of transaction.

\n","key":"LoyaltyRatePerUnit","type":"text","value":""},{"description":"

Comprised of the following fields:\nCardName\nEmail\nBillingAddress1\nBillingAddress2\nBillingCity\nBillingState\nBillingZIP

*If any part of the Billing address is sent through, then BillingAddress1, BillingCity, BillingState and BillingZIP must be supplied.

\n","key":"Billing Address","type":"text","value":""},{"description":"

Comprised of the following fields:\nShippingAddress1\nShippingAddress2\nShippingCity\nShippingState\nShippingZIP

*If any part of the Shipping address is sent through, then ShippingAddress1, ShippingCity, ShippingState and ShippingZIP must be supplied.

\n","key":"Shipping Address","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

Post an AUTH against a particular card. An authorization needs to be subsequently forced into the batch using the FORCE command.

Transaction Request, Form Action & Method:

For an AUTH the calling form should be set to use the POST method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp

\n\n

e.g. <form action=\"https://safepaycert.paymentlogistics.net/transaction.asp\" method=\"post\">\n\n

Mandatory Parameters

TxnType: This can be set to either SALE or AUTH

MerchantID: This needs to be set to the account Username used to login to the portal

OrderID: A unique alphanumeric reference that you can use to identify an individual order

Amount: The amount of the transaction not including the currency symbol. (As 0000.00)

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
MerchantID
Amount (Format as 0000.00)
OrderID

See the next section regarding generation of Hash values.

Optional Parameters

ReturnURL: The page to load once the payment process is complete.

CancelURL: The page to return to should the customer quit the transaction before completion

Description: A text description for the item being purchased

Options: When passed NOADDRESS will skip requesting a credit card address

When passed RETURNONERROR the ReturnURL will be immediately loaded even if the transaction fails or is declined.

Points - The default value type for loyalty
Punches - GoLarge - Stores against the Punches value type under the promotion GoLarge

Contact us regarding our loyalty programs if you would like these features enabled on your account.

LoyaltyRatePerUnit: The ratio of loyalty points issued to dollars spent. For instance, if the value is 100 then 100 points will be issued for each dollar of transaction.

Billing Address: Comprised of the following fields:

CardName
Email
BillingAddress1
BillingAddress2
BillingCity
BillingState
BillingZIP

If any part of the Billing address is sent through, then BillingAddress1, BillingCity, BillingState and BillingZIP must be supplied.

Shipping Address: Comprised of the following fields:

ShippingAddress1
ShippingAddress2
ShippingCity
ShippingState
ShippingZIP

If any part of the Shipping address is sent through, then ShippingAddress1, ShippingCity, ShippingState and ShippingZIP must be supplied.

Transaction Response

Following a successful transaction the following 3 events will occur:

An email will be received at the profile email address notifying that an order has been raised.
The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
OrderID: The order reference supplied
Amount: The amount of the transaction
PNRef: The Transaction reference (used for FORCE, VOID, CREDIT etc)
Result: The status of the transaction, 0 for success
TxnType: Either SALE or AUTH in this instance
Last4: The last 4 digits of the card
CardType: The type of card processed (Mastercard, Visa etc)

The following fields will be posted back to your receiving form if (enabled in the profile)

OrderID: The order reference supplied
Description: The product / order description
Amount: The amount of the transaction
TxnType: Either SALE or AUTH in this instance
Hash
BillingFirstName, BillingLastName, BillingEmail, BillingAddress1, BillingAddress2, BillingCity, BillingState, BillingZIP
ShippingAddress1, ShippingAddress2, ShippingCity, ShippingState, ShippingZIP
PNRef: The Transaction reference (used for FORCE, VOID, CREDIT etc)
AuthCode: The credit card authorization code
Last4: The last 4 digits of the card
CardType: The type of card processed (Mastercard, Visa etc)

The Hash value returned in the Postback URL is made up of the following values. (See Section 5.1 for further details)

SharedSecretKey
MerchantID
Amount
OrderID
PNRef

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
Amount,
OrderID,
PNRef

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"f19386c0-d74d-427c-8db7-2e67e248bcfa"},{"name":"TRANSPARENT REDIRECT for SALE and AUTH","id":"c6bd617d-b260-45bc-85ac-6f989c2aa615","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*This can be set to either SALE or AUTH (required)

\n","key":"TxnType","type":"text","value":""},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*A unique alphanumeric reference that you can use to identify an individual order (required)

\n","key":"OrderID","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"Amount","type":"text","value":""},{"description":"

\n","key":"Hash","type":"text","value":""},{"description":"

*The page to load once the payment process is complete.

\n","key":"ReturnURL","type":"text","value":""},{"description":"

*This credit card number or PAN (required)

\n","key":"CardNumber","type":"text","value":""},{"description":"

*The users name as it appears on the card (required)

\n","key":"CardName","type":"text","value":""},{"description":"

*The card expiry month as two digits (required)

\n","key":"ExpMonth","type":"text","value":""},{"description":"

*The card expiry year as two digit (required)

\n","key":"ExpYear","type":"text","value":""},{"description":"

*An alternative field including both values instead of ExpMonth and ExpYear separately, valid values can be mmyy or mm/yy (required)

\n","key":"ExpDate","type":"text","value":""},{"description":"

*The 3 digit number from the back of the card if required. (required)

\n","key":"CVNum","type":"text","value":""},{"key":"BillingZip","value":"","description":"

*The ZIP Code of the billing address, for Address Validations.

\n","type":"text"},{"key":"BillingAddress1","value":"","description":"

*The Street of the billing address, for Address Validations.

\n","type":"text"}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

In addition to using the Payment Logistics screens to capture and process card payments it is possible to allow users to enter full credit card details on your own web forms, where the user would be unaware that they had been transferred to a 3rd party payment screen at all. This only works for SALE and AUTH type transactions. You setup your form in exactly the same way as mentioned above in the section on SALE and AUTH.

Mandatory Parameters:

TxnType: This can be set to either SALE or AUTH

MerchantID: This needs to be set to the account Username used to login to the portal

OrderID: A unique alphanumeric reference that you can use to identify an individual order

Amount: The amount of the transaction not including the currency symbol. As (Format as 0000.00)

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
MerchantID
Amount (Format as 0000.00)

ReturnURL: The page to load once the payment process is complete.

CardNumber: This credit card number or PAN

CardName: The users name as it appears on the card

ExpMonth: The card expiry month as two digits

ExpYear: The card expiry year as two digits

ExpDate: An alternative field including both values instead of ExpMonth and ExpYear separately, valid values can be mmyy or mm/yy

CVNum: The 3 digit number from the back of the card if required.\n

BillingZip: The ZIP Code of the billing address, for Address Validations.\n

BillingAddress1: The Street of the billing address, for Address Validations.

Note: The optional parameters available in SALE and AUTH are not valid for Transparent Redirect.

On submitting the form, the transaction values along with the card details will be immediately posted and processed and your return URL will be called with the transaction status being passed back to say whether the transaction was approved or declined.

Please note you must use an MD5 hash for the transaction when working with transparent redirect. You will need to calculate the hash from the transaction details on a previous page before offering the additional card fields for input as there will be no opportunity to calculate the has as the transaction is processed.

Transaction Response:

Following a successful transaction the following 3 events will occur:

An email will be received at the profile email address notifying that an order has been raised.
The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
OrderID: The order reference supplied
Amount: The amount of the transaction
PNRef: The Transaction reference (used for FORCE, VOID, CREDIT etc)
Result: The status of the transaction, 0 for success
TxnType: Either SALE or AUTH in this instance

The following fields will be posted back to your receiving form if (enabled in the profile)

OrderID: The order reference supplied
Amount: The amount of the transaction
TxnType: Either SALE or AUTH in this instance
Hash
PNRef: The Transaction reference (used for FORCE, VOID, CREDIT etc)
AuthCode: The credit card authorization code

The Hash value returned in the Postback URL is made up of the following values.

SharedSecretKey
MerchantID
Amount
OrderID
PNRef

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
Amount,
OrderID,
PNRef

Warning:

No opportunity will be given to the user to preview their transaction before it is posted, so you will need to communicate on the web page that when the button is pressed their transaction will be completed. Also, while there is no requirement for you to have the form on a secure SSL encrypted page, it may put purchasers off if they don't see the outbound page being secure itself. There is no risk, but psychologically the user may think it will be an insecure transaction. We encourage you to therefore use an SSL certificate for outbound forms and return URL's.

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"c6bd617d-b260-45bc-85ac-6f989c2aa615"},{"name":"FORCE","id":"87d6f606-d939-4da1-b96b-79eec963d17d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*Set to FORCE (required)

\n","key":"TxnType","type":"text","value":"FORCE"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*The transaction reference from a previous AUTH (required)

\n","key":"PNRef","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"Amount","type":"text","value":""},{"description":"

\n","key":"Hash","type":"text","value":""},{"description":"

The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

\n","key":"ReturnURL","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

FORCE captures or forces an existing AUTH into the batch for completion of the transaction. This function runs directly without interaction from a user (no form fields to input)

Transaction Request, Form Action ; Method:

For FORCE, the calling form should be set to use the POST or GET method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp

\n\n

Mandatory Parameters:

TxnType: Set to FORCE

MerchantID: This needs to be set to the account Username used to login to the portal

PNRef: The transaction reference from a previous AUTH

Amount: The amount of the transaction not including the currency symbol. (As 0000.00)

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
MerchantID;
Amount (Format as 0000.00)
PNRef

Optional Parameters:

ReturnURL: The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

Transaction Response

Following a successful transaction the following 2 events will occur:

The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
Amount: The amount of the transaction
PNRef: The Transaction reference;
Result: The status of the transaction, 0 for success
TxnType: FORCE

The following fields will be posted back to your receiving form if (enabled in the profile):

Amount: The amount of the transaction
TxnType: FORCE
Hash;
PNRef: The Transaction reference;
AuthCode: The credit card authorization code
Merchant ID
Amount

The Hash value returned in the Postback URL is made up of the following values.

SharedSecretKey;
MerchantID;
Amount;
PNRef

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
Amount,
PNRef

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"87d6f606-d939-4da1-b96b-79eec963d17d"},{"name":"VOID","id":"51390d4d-2cba-464f-9ec4-0ee2d315d654","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*Set to VOID (required)

\n","key":"TxnType","type":"text","value":"VOID"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*The transaction reference from a previous AUTH

\n","key":"PNRef","type":"text","value":""},{"description":"

\n","key":"Hash","type":"text","value":""},{"description":"

The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

\n","key":"ReturnURL","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

Voids an existing transaction that hasn't yet been submitted into a batch. This function runs directly without interaction from a user (no form fields to input)

Transaction Request, Form Action & Method:

For VOID the calling form should be set to use the POST or GET method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp

Mandatory Parameters:

TxnType: Set to VOID

MerchantID: This needs to be set to the account Username used to login to the portal

PNRef: The transaction reference from a previous AUTH/SALE

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 3 pieces of information:

SharedSecretKey (found in the profile page of the portal)
MerchantID;
PNRef

Optional Parameters:

ReturnURL: The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

Transaction Response:

Following a successful transaction the following 2 events will occur:

The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
PNRef: The VOID transaction reference;
Result: The status of the transaction, 0 for success
TxnType: VOID
AuthCode: The credit card authorization code

The following fields will be posted back to your receiving form if (enabled in the profile)

Hash;
PNRef: The VOID transaction reference;
AuthCode: The credit card authorization code

The Hash value returned in the Postback URL is made up of the following values.

SharedSecretKey
MerchantID
PNRef
AuthCode

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
PNRef
AuthCode

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"51390d4d-2cba-464f-9ec4-0ee2d315d654"},{"name":"CREDIT","id":"27d34ccc-a9eb-4821-af0e-fc31b8834408","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*Set to CREDIT (required)

\n","key":"TxnType","type":"text","value":"CREDIT"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"Amount","type":"text","value":""},{"description":"

*The transaction reference from a previous SALE or AUTH/FORCE. If not supplied a card number will be required during the process. (required)

\n","key":"PNRef","type":"text","value":""},{"description":"

\n","key":"Hash","type":"text","value":""},{"description":"

The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

\n","key":"ReturnURL","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

A CREDIT returns funds to the card for a SALE that has been completed and submitted to the batch. This function runs directly without interaction from a user (no form fields to input) when a PNRef is sent in otherwise a page will be used to capture the complete card details.

Transaction Request, Form Action & Method:

For CREDIT the calling form should be set to use the POST or GET method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp.

Mandatory Parameters:

TxnType: Set to CREDIT

MerchantID: This needs to be set to the account Username used to login to the portal

Amount: The amount of the transaction not including the currency symbol. (As 0000.00)

PNRef: The transaction reference from a previous SALE or AUTH/FORCE. If not supplied a card number will be required during the process.

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
MerchantID
Amount (Format as 0000.00)
PNRef

Optional Parameters:

ReturnURL: The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

Transaction Response:

Following a successful transaction the following 2 events will occur:

The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
Amount: The amount of the transaction
PNRef: The CREDIT transaction reference
Result: The status of the transaction, 0 for success
TxnType: CREDIT

The following fields will be posted back to your receiving form if (enabled in the profile):

Amount: The amount of the transaction
Hash
PNRef: The CREDIT transaction reference
AuthCode: The credit card authorization code

The Hash value returned in the Postback URL is made up of the following values.

SharedSecretKey
MerchantID
Amount
PNRef

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
Amount
PNRef

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"27d34ccc-a9eb-4821-af0e-fc31b8834408"},{"name":"ADDCARD","id":"d4fb9550-58a8-4299-870d-16735b0a5379","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*Set to ADDCARD (required)

\n","key":"TxnType","type":"text","value":"ADDCARD"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 3 pieces of information:

SharedSecretKey (found in the profile page of the portal)\nTxnType\nMerchantID

(required)

\n","key":"Hash","type":"text","value":""},{"description":"

A unique identifier that you can use to refer to your customer.

\n","key":"CustomerID","type":"text","value":""},{"description":"

The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

\n","key":"ReturnURL","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

Uses a web page to gather card and customer information that can be stored for future billing.

Transaction Request, Form Action & Method:

For ADDCARD the calling form should be set to use the POST or GET method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp

Mandatory Parameters:

TxnType: Set to ADDCARD

MerchantID: This needs to be set to the account Username used to login to the portal

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 3 pieces of information:

SharedSecretKey (found in the profile page of the portal)
TxnType
MerchantID

Optional Parameters:

CustomerID: A unique identifier that you can use to refer to your customer.

ReturnURL: The page to load once the transaction is complete. If none is supplied a basic web page will be displayed on completion of the request.

Transaction Response:

Following a successful transaction the following 2 events will occur:

The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
Result: The status of the transaction, 0 for success
TxnType: ADDCARD
CustomerID: The supplied token sent in
CcInfoKey: The unique handle to this card used for future billing
CustomerKey: The unique handle to the customer details for future reference

The following fields will be posted back to your receiving form if (enabled in the profile):

TxnType: ADDCARD in this instance
Hash
MerchantID: The MerchantID supplied.
CcInfoKey: The unique handle to this card used for future billing
CustomerKey: The unique handle to the customer details for future reference

The Hash value returned in the Postback URL is made up of the following values.

SharedSecretKey
MerchantID
CustomerKey
CCInfoKey

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
CustomerKey
CCInfoKey

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"d4fb9550-58a8-4299-870d-16735b0a5379"},{"name":"UPDATECARD","id":"fe121590-d956-42d2-97f5-fdf65810841a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*Set to UPDATECARD (required)

\n","key":"TxnType","type":"text","value":"UPDATECARD"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*The existing Customer ID from a previous call to ADDCARD (required)

\n","key":"CustomerKey","type":"text","value":""},{"description":"

*The existing Credit Card ID from a previous call to ADDCARD (required)

\n","key":"CcInfoKey","type":"text","value":""},{"description":"

*A unique identifier that you can use to refer to your customer. (required)

\n","key":"CustomerID","type":"text","value":""},{"description":"

*This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)\nTxnType\nMerchantID \nCcInfoKey

(required)

\n","key":"Hash","type":"text","value":""},{"description":"

The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

\n","key":"ReturnURL","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

Update an existing card and owner's details that have already been added via ADDCARD.

Transaction Request, Form Action & Method:

For UPDATECARD the calling form should be set to use the POST or GET method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp.

Mandatory Parameters:

TxnType: Set to UPDATECARD

MerchantID: This needs to be set to the account Username used to login into the portal

CustomerKey: The existing Customer ID from a previous call to ADDCARD

CcInfoKey: The existing Credit Card ID from a previous call to ADDCARD

CustomerID:A unique identifier that you can use to refer to your customer.

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
TxnType
MerchantID
CcInfoKey

Optional Parameters:

ReturnURL: The page to load once the transaction is complete. If none is supplied a basic web page will be displayed on completion of the request.

Transaction Response:

Following a successful transaction the following 2 events will occur:

The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client-side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
Result: The status of the transaction, 0 for success
CustomerID: The supplied token sent in
CcInfoKey: The unique handle to this card used for future billing
CustomerKey: The unique handle to the customer details for future reference
TxnType: UPDATECARD

The following fields will be posted back to your receiving form if (enabled in the profile):

TxnType: UPDATECARD in this instance
Hash
Cardholder: The cardholders name
CustomerID: The supplied token sent in
CcInfoKey: The unique handle to this card used for future billing
CustomerKey: The unique handle to the customer details for future reference

The Hash value returned in the Postback URL is made up of the following values.

SharedSecretKey
MerchantID
CustomerKey
CcInfoKey

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
CustomerKey
CcInfoKey

","urlObject":{"protocol":"https","path":["transaction.asp"],"host":["safepaycert","paymentlogistics","net"],"query":[],"variable":[]}},"response":[],"_postman_id":"fe121590-d956-42d2-97f5-fdf65810841a"},{"name":"BILLCARD","id":"dce4382c-12c0-4b65-9f61-922b1f0619b7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"description":"

*Set to BILLCARD (required)

\n","key":"TxnType","type":"text","value":"BILLCARD"},{"description":"

*This needs to be set to the account Username used to login to the portal (required)

\n","key":"MerchantID","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"Amount","type":"text","value":""},{"description":"

*The amount of the transaction not including the currency symbol. (As 0000.00) (required)

\n","key":"CcInfoKey","type":"text","value":""},{"description":"

*This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)\nTxnType\nMerchantID \nAmount (Format as 0000.00)

(required)

\n","key":"Hash","type":"text","value":""},{"key":"ReturnURL","type":"text","value":""}]},"url":"https://safepaycert.paymentlogistics.net/transaction.asp","description":"

Posts a SALE transaction against a stored card added via ADDCARD.

Transaction Request, Form Action & Method:

For BILLCARD the calling form should be set to use the POST or GET method and have an action property of https://safepaycert.paymentlogistics.net/transaction.asp.

Mandatory Parameters:

TxnType: Set to BILLCARD

MerchantID: This needs to be set to the account Username used to login to the portal

Amount: The amount of the transaction not including the currency symbol. (As 0000.00)

CcInfoKey: The existing Credit Card ID from a previous call to ADDCARD

Hash: This is the MD5 Hash value used to verify that the data passed is originating from the calling form. It is generated from the following 4 pieces of information:

SharedSecretKey (found in the profile page of the portal)
TxnType
MerchantID
Amount (Format as 0000.00)

Optional Parameters:

ReturnURL: The page to load once the transaction is complete. As this function has no form input an XML result will be returned if the ReturnURL is left blank.

Transaction Response:

Following a successful transaction the following 3 events will occur:

An email will be received at the profile email address notifying that an order has been raised.
The Return URL will be passed the following parameters (if enabled in the profile) either following the ? as a GET or following the anchor # for retrieval via client side javascript.

Hash: The hash of the order for validation purposes
MerchantID: The MerchantID supplied
Amount: The amount of the transaction
PNRef: The transaction reference
Result: The status of the transaction, 0 for success
TxnType: SALE

The following fields will be posted back to your receiving form if (enabled in the profile):

Amount: The amount of the transaction
Hash
PNRef: The transaction reference
AuthCode: The credit card authorization code

The Hash value returned in the Postback URL is made up of the following values. (See Section 5.1 for further details)

SharedSecretKey
MerchantID
Amount
PNRef

The Hash value returned in the Return URL is made up of the following values.

SharedSecretKey
ReturnURL
MerchantID
Amount,
PNRef

While it is useful to use the Button and Form generators to create the simple forms and necessary code required to integrate with Paygistix Web, you can also create your own forms using the same types of parameters as seen for Buttons & Forms.

The SDK is called using regular HTTP Forms.

\n","event":[{"listen":"prerequest","script":{"id":"f7ea2a86-fb64-45b9-822f-6539fb25f59c","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"69dc3611-9cfe-41bf-81b6-42759da1c2d8","type":"text/javascript","exec":[""]}}],"_postman_id":"bd159400-ce0b-4d42-8f7e-ff1ed690e406"}],"event":[{"listen":"prerequest","script":{"id":"28ef2fc1-51be-4c6b-9c85-b5df0e6e05d4","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"62ff690e-ce02-4d34-9640-a56583f8b49f","type":"text/javascript","exec":[""]}}]}