Skip to main content

Migration from Hosted Redirect to LC Direct

Latitude's Hosted Redirect solution provided a simple method for Merchant partners to integrate the Latitude Interest Free secure payment page. This has now been redesigned to form a new checkout experience called Latitude Checkout.

Quick Comparisons between Hosted Redirect and Latitude Checkout Direct#

FeatureLatitude Hosted RedirectLatitude Checkout Direct
BenefitsLatitude's basic secure payment page to accept interest free payments.Latitude provides an enhanced secure payment page plus additional checkout features:
logic to handle Merchant-customised processing rules
promotions are managed by Latitude
in-checkout (Latitude Checkout) discounts
common framework for ecommerce and instore integrations
+pay by Latitude Customer wallet
+express customer checkout from product page
+checkout using Merchant and Latitude issued giftcards

+ indicates features coming soon
SecurityPCI-DSS certification is maintained by Latitude. Signed-hash HMAC protection for all URL query strings.PCI-DSS certification is maintained by Latitude. Merchants are authenticated using secure Merchant secrets.
ScalabilityA simple, static secure payment page to capture card or account number payment details.Multi-functional secure payment page to handle promotions and card/account payment details.
Offers flexibility for Latitude to enhance with additional features.
Integration MethodRedirects the Customer away from Merchant sites during the checkout, using parameters within a HTTPS GET URL query string.Redirects the Customer away from Merchant sites during the checkout using API requests over HTTPS POST. addtional customer, cart and product details are required in the payload.
Latitude handles the promotion logic and checks for product exclusions (if applicable).

How to Migrate to Latitude Checkout Direct#

In the Hosted Redirect integration, Merchants are provided with unique userName, shared secret and configId.
Merchants are required to build a URL query string containing parameters which are unique to Latitude's HTTPS GET endpoint.
The parameters included fields such as username, configId, merchReference, currency, amount, formType, txnType, LFSData.terminalId, ecm, requestorIp, LFSData.promoCode, LFSData.promoDescription and LFSData.items (for line item information), with optional field LFSData.storeMid.
The URL query string is protected with verifyMessage, a HMAC calculation on the whole string using the shared secret.

To migrate to Latitude Checkout Direct,

  1. Existing credentials for the Hosted Redirect cannot be used. Merchants will be provided with new credentials - Merchant ID, Merchant Secret. For more information, refer to Setup Pre-requisite Requirements.
  2. URL Query strings are not supported, thus the integration flow contains multiple steps to build different API payloads: Purchase Request and Verify Request as described in Integration Flow.
  3. All payloads are sent to Latitude's API endpoints /purchase or /purchase/verify using HTTPS POST with Basic Authentication.

    Note: the Purchase Request payload contains a JSON formatted list of customer details, addresses (shipping, billing) and order line details. Additionally, merchantUrls allow Latitude Checkout to redirect the Customer back to the Merchant's site upon completion or cancellation (return to cart) of the payment.

  4. In the Purchase Response, Latitude will return a parameter called redirectUrl, used by the Merchant to redirect the Customer to Latitude's secure payment page.
  5. After the Customer's payment has been completed, Latitude will redirect the Customer to the complete URL as provided in merchantUrls. The complete Url is used regardless whether the transaction is approved or declined.
  6. All Merchants must perform the Verify Request after receiving the Purchase Response. Verify Requests will allow the outcome of the payment to be determined, using result (approved transactions will show result=completed, or declined transactions will show result=failed).
  7. Important reference parameters that are returned in the Verify Response include transactionReference and gatewayReference. These are references assigned by Latitude Checkout and should be saved against the transaction/order. The gatewayReference will be used when Order Management is required (voids, capture or refunds).

Detailed Latitude Checkout Direct Information#

Detailed Latitude Checkout Direct information can be found at Direct Integration for Custom eCommerce Platforms.