Overview

Introduction

Pyxis provides a hosted payment page which allows users to enter payment details securely on a branded page*.

This allows Pyxis tenants to create a url to which they can direct their users.

Users can then check the amount the amount they owe, and enter their debit card details etc. Once the user submits their payment details, Pyxis will process the payment, and let the user know whether it succeeded correctly.

The hosted payment system can be also be configured with a call backs that will be fired when the payment succeeds or fails. These can be used to trigger third party systems to reflect the status of a payment. They can also be used to instruct Pyxis to take some action (for example, to complete the allocation of an asset to an acquirer.

Process Overview

The process for receiving a payment via the hosted payment page is as follows.

1) Tenant requests a payment url from the hosted payment system (https://pay.nfiniti.co). This request must include the following information:

• The amount due,
• The id of the customer from whom the payment is due.
• The id of a vault belonging to the customer, into which the funds will be placed on success.
• A description of the reason for the payment.

And, optionally:

• A callback url to be called on successful payment
• A callback url to be called if a payment fails.
• Application specific meta data regarding the payment.

2) The tenant then directs the customer to the url returned by the hosted payments page, either by url, redirect etc.

3) The customer fills in required details and submits the payment

4) Pyxis processes the payment
If the payment is by debit card, a completed (failed or succeeded) payment record will be created in the Pyxis system against the customer.
If the payment succeeds the relevant amount will be credited to the customers vault.
* If the payment is via bank transfer, a pending payment record will be created against the customer. The payment will complete when the funds arrive in the Pyxis bank account.

**5) If specified when the url was requested, the appropriate callbacks will be triggered. These callbacks contain details of the payment created, and the application specific metadata supplied during the request.