Integrated Payment Pages

Payrix offers two hosted payment options that integrate directly with an online platform or website checkout page, allowing for secured payment processing and simplified PCI compliance:

• Hosted Payment Page

• electronic Direct Debit Request (eDDR)

Hosted Payment Page (HPP)

The HPP is used to take a Real Time ecommerce style payment. This can be used to take a payment from Credit or Debit card, with an immediate response to if the transaction is settled or rejected.

• This works by you populating the API with first name, surname and email address, etc and a return URL.

• We then respond with a branded URL to redirect the payer to, the payer then completes their details and accepts the terms and conditions if you are saving the Payer.

• We will then redirect them back to your site using the return URL.

• You then use the Token Look Up call to confirm the page was completed as expected and find the transaction status.

  • You should allow up to 5 seconds once the re-direct has triggered the payer back to the return URL.

If you require additional customisation, you have the option to build your own HPP. This can be achieved using the Building a Webpage model, however you will need to adhere to some compliance rules which can be found here.

electronic Direct Debit Request (eDDR)

An eDDR is used when you wish to debit a Payers card or bank account on your schedule. If you wish to trigger the transaction from your system, rather than the customer initiating the transaction you need to have an “authority to debit”. This is a legal compliance document that allows you to debit the Payers account.

The authority to debit could be a verbal recording, a signed paper document of a web form with certain wording, capture etc. We offer a hosted solution to capture the bank and card details in a PCI compliant and with adhering to the authority to debit rules.

• This works by you populating the API with name, address details etc and a return URL.

• We then respond with a branded URL to redirect the payer to, the payer then completes their details and accept the terms and conditions.

• We will then redirect them back to your site using the return URL.

• You then use the Token Look Up call confirm the page was completed as expected.

  • You should allow up to 5 seconds once the re-direct has triggered the payer back to the return URL.

• A Confirmation email is also sent to the payer automatically from Payrix.

As debit transactions take 2 business days to Settle or Reject you must use the two Status Changes calls to track how the transactions is processing and its end result. Once you have retrieved each Status you can acknowledge the transaction to remove it from the result set until the next status change occurs. More details can be found here - How to Process a Bank Debit / Card Debit.

You have the option to build your own eDDR, if you wish to go down this route, you will need to adhere to some compliance rules which can be found here.

Overview of Features

• Less PCI requirements by the merchant as the data is handled by Payrix and are PCI Level 1 Compliant

• Works off a redirection from your page to our page, then redirects back to your nominated page

• Has built in captcha

• Ability to save payer

• 3DS v2 functionality available (HPP)

• Acceptance of wallet payments (Apple Pay and Google Pay) for Australia and New Zealand (HPP)

• Ability to have logo and company colours

• Automatically sends confirmation email receipt to the payer (eDDR)