![](\"https://why.pay.link/images/DeveloperCenter/web_login3.png\")
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.
\r\nIntegrators should have a basic understanding of HTML.
\r\nTo use some of the more advanced features including security hash value generation, knowledge of server side website development is required.
\r\nPlease contact Payment Logistics support if you require further information.
\r\nLogin with issued username and password for the Paygistix Web portal at: https://safepaycert.paymentlogistics.net
\r\n\r\nFollowing a successful login you should see the following page.
\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_home.png\")
\r\nChoose Account Profile, from the portal menu.
\r\nThis is the main configuration screen for the merchant. Complete the options as required.
\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_profile2.png\")
\r\nUsername
\r\nThe username used to login to the admin portal, also used to identify the correct account at code level from Buttons, Forms and Custom integrations.
\r\nPassword
\r\nThe 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.
\r\nDirect Gateway Authentication
\r\nWith this option selected, the above username and password are authenticated directly against the Payment Logistics payment gateway and used for processing transactions.
\r\nGateway Username
\r\nUsername issued for access to the Payment Logistics payment gateway. Not available when \"Direct Gateway Authentication\" is selected.
\r\nGateway Password
\r\nPassword issued by Payment Logistics. Not available when \"Direct Gateway Authentication\" is selected.
\r\nGateway Vendor ID
\r\nVendor ID issued by Payment Logistics. Not required when \"Direct Gateway Authentication\" is selected as this is set automatically.
\r\nSecret Hash Key
\r\nThis 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.
\r\nCards Accepted
\r\nChoose which cards you wish to accept on the payment screen.
\r\nMerchant Name
\r\nName that is displayed on payment screens.
\r\nEmail Address
\r\nEmail address to which successful payment confirmations and order information will be sent.
\r\nEnable Postback
\r\nIf 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.
\r\nPostback URL:
\r\nThe 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.
\r\nUse HTTP Get Rather than POST
\r\nWhen 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.
\r\nAdditional Options
\r\nSet additional flags regarding the payment process as follows.
\r\nDetermines which geographies are supported, US only, US & Canada, Whole World.
\r\nFields allowing the customer to enter a different shipping address from the billing address provided during the checkout process.
\r\nThe three digits on the back of a card (four on the front for AMEX) required when accepting payments becomes mandatory when checked.
\r\nWhen enabled customer will be prompted to enter an email address during the transaction process.
\r\nSends a customer an order acknowledgment email on completion of a transaction.
\r\nSends the merchant an order acknowledgment email on completion of a transaction.
\r\nRequires a user to check the box next to terms and conditions before continuing with the transaction.
\r\nReturn URL Parameter Passing Method
\r\nWhen 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.
\r\nReturn on Error and Success States
\r\nTypically 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.
\r\nCustom Logo
\r\nAllow 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.
\r\nTerms & Conditions Text
\r\nThis is the merchant configurable text to show on the popup Terms & Conditions window if Terms & Conditions are enforced.
\r\nUse 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.
\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_taxes.png\")
\r\nThe 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.
\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_button.png\")
\r\nButton Text
\r\nThis 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\".
\r\nValue Range
\r\nTo 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.
\r\nReturn URL
\r\nThis 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.
\r\nExample code generated by the Button Generator:
\r\n \r\n```\r\n\r\n```\r\n \r\nThe 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:
\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_payBtn2.png\")
\r\nPressing the button takes you to the payment page where the amount is already selected.
\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_payment2.png\")
\r\nThe 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.
\r\n![](\"https://why.pay.link/images/DeveloperCenter/webForm_fill.png\")
\r\nProduct lines (multiple rows)
\r\nCode, Description & Price
\r\nYou 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.
\r\nReturn URL
\r\nThis 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\"
\r\nTransaction Type
\r\nYou 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.
\r\nCapture Fields
\r\nYou 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
\r\nThe 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:
\r\n \r\n```\r\n\r\n\r\n```\r\n\r\nThe resulting form looks like this in a browser and can be easily styled with CSS:
.\r\n![](\"https://why.pay.link/images/DeveloperCenter/web_cart2.png\")
Both when calling the payment gateway and receiving a postback you can use an MD5 hash value to validate that the call is authenticated.
\r\nWe 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.
\r\nIn 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.
\r\nWhen coding your own integrations to the Paygistix Web service you will need to generate your own Hash value. Here is some example pseudo code:
\r\n \r\n```\r\nString InputValue = SharedSecretKey + MerchantID + Amount + OrderID\r\nString HashValue = MD5(InputValue)\r\n```\r\n \r\nTransparent 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:
\r\n \r\n```\r\nString InputValue = SharedSecretKey + MerchantID + Amount \r\nString HashValue = MD5(InputValue)\r\n```\r\n \r\nThere 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.
\r\nAs 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.
\r\nWithin 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.
\r\nOn successful completion of a transaction, the website will return to a predefined URL passed in via the calling form.
\r\nThe following parameters will be available (depending on the function called)
\r\n