HPP (Hosted Pay Page)

ConnexPay’s Hosted Pay Page allows for collecting credit card data securely - without it ever touching your system.

You can easily integrate with our hosted payment page in order to capture sales transactions. This means you don’t need to be fully PCI compliant - we’ll capture and encrypt cardholder data so you don’t need to.

  • Your customer will start on your website and place their order.
  • You transmit that sale information to us.
  • You redirect your customer to our hosted payments page where they will be asked to key in their pertinent credit card information.
  • Once saved, we will make the authorization attempt. If successful, the customer will see an option to either cancel the transaction or to “Make Payment”. ConnexPay will then redirect your customer to a URL supplied by you in the initial hosted payment page request.
  • If the authorization is not successful the customer will be asked if they want to try again. If yes the credit card entry form will display with all fields empty. If no, the customer will go back to your website.
  • Once a sale is successfully authorized, CXP will post a response back to you with all applicable sales information.
  • If the sale is not successfully authorized CXP will post a response back to you that indicates the sale was not successful.

Implementation Guide

Introduction

We provide the ability for you to have ConnexPay accept consumer credit card information on a form served by ConnexPay as part of your client’s check-out process, thus eliminating the need for you to accept, store and/or forward consumer credit card information to ConnexPay from your software.

We refer to this as Hosted Payment. The Process steps include:

  1. Your customer completes selections on your website and proceeds to “check out”
  2. You process the customer’s shopping basket
    • Format a typical ConnexPay sale API request but don’t include consumer credit card information.
  3. You make a HostedPaymentPage Request from ConnexPay API
    • The request body includes the sale request object formatted in step 2.
    • Also in the request is a URL resultRedirectUrl we will use to route your customer back to you upon completion or error of the credit card input activity.
  4. You will receive a HostedPayment tempToken from ConnexPay in response to step 3.
    • You will redirect your customer to the following URL using that tempToken: https://sales.connexpay.com/#!/HostedPaymentPage/{tempToken}. For example: https://sales.connexpay.com/#!/HostedPaymentPage/23551d7b-c563-445d-9716-f39006024087
  5. Your customer completes the credit card form and submits.
  6. We extract the detailed sale request submitted in step 3 and we apply the customer’s card payment information.
  7. We complete the sale process
  8. We redirect a successful sale completion, cancellation of credit card form, and errors to resultRedirectUrl

Once on our Hosted Payments Page:

  1. Your customer sees a form allowing them to input credit card information
  2. They have the options to:
    • RESET - Clears the form of any entered data in the event the user needs to re-key
    • CANCEL - Returns your customer to your website. The transaction is not processed
    • MAKE PAYMENT - Processes the sale

ConnexPay Processes the Sale

Once your customer selects MAKE PAYMENT we will combine the customer-supplied card information with the sale request body associated with the temp token and complete our fraud check and authorization process.

ConnexPay Redirects To Client

The Sale Receipt is the response to a client call to
GET https://saleapi.connexpay.com/api/v1/sales/{tempToken}

You make this call immediately upon redirection and process an appropriate receipt for your customer.

Success or failure of the fraud check or consumer credit card authorization is ascertained from the GET sale response, so it is required to make the GET call back to ConnexPay with the SaleGuid in order to confirm success for a client.

Error Handling

Form re-submission

If your customer resubmits a form for a successful sale or a failed authorization on a previously used tempToken, no action occurs on their credit card. On submit of the form for this repeated attempt we redirect them to you with no attempted action on their card. If this occurs you can look up the sale associated with the tempToken and inform your customer that this is a repeated attempt on a stale form and that no charges have occurred.

Sample:


Did this page help you?