For bookings not made online or when additional payments are required.
To take a payment, you will need to go to the payments screen in the booking by either selecting Payments in the Finance tab or a Finance Summary pop up screen.
Once in the payment screen, you will notice that there are DPS options in the Payment Method drop down option:
- DPS Purchase - Select if adding a new payment.
- DPS Capture - Select if capturing card data
- DPS Auth - Select if getting authorisation for a payment.
- DPS Charge (PXPost service only) - Select if taking a subsequent payment from the customer's card.
Depending on which option you select will determine what to do from here.
- Select who the payment is being Paid in by, the Payment Amount, and any comments if necessary (but leaving the Pay Ref field blank as this is required for the DPS reference)
- Click Save.
- The screen will refresh and the DPS logo will then appear on screen
- Click on the DPS logo to open up the DPS payment screen so you can enter the card details.
- The payment will then be processed.
- Once the payment has been processed, click Next to exit the DPS pop up and the payment will be shown on the payments screen for that booking with DPS's Payment reference number
- You can then Exit the payment screen.
To use any of the features below you will need to be registered for the PXPay service with DPS.
- If DPS Auth is selected, no funds are actually transferred so the resulting payment record in iBex will show as the amount being crossed out and being 'Held'.
- You process an authorisation the same way as a DPS Purchase so please follow the instructions above.
To subsequently process the funds that have been authorised, you can perform a DPS Complete transaction. Follow the instructions below.
- Click on Edit at the end of the held payment line,
- Select the payment method DPS Complete
- Click Save.
- There may be a 10-15 second delay while the transaction is being processed but once successful, a new payment record will be added to the payment screen.
As you can see above, the Pay Ref (which is automatically provided by DPS) is the same for both payment records as the card charged is the same one.
To use any of the features below you will need to be registered for the PXPay service with DPS.
When a payment is processed via DPS (whether a Purchase or an Auth, or a credit card is stored via DPS Capture), a 'token' is held against the booking which allows further charges to be made against the customer's card. If you are making a new payment and a token is held in that booking, DPS Charge will be an option in the payment methods to select from. If selected, the same card that was originally charged will be charged any amount entered when the Save button is clicked.
As you can see above, the original payment was a DPS Purchase and the subsequent one (highlighted) was a DPS Charge payment.
Please note that DPS Tokens will never expire, so you can create further payments against this card whenever necessary.
When one or more tokens have been saved against a booking or itinerary sale, the Charge option shows and, when selected, will allow the operator to choose from one of the 6 most recently saved card tokens.
To use any of the features below you will need to be registered for the PXPay service with DPS.
- If DPS Capture is selected, card data will be tokenized, funds will not be pre-authorised.
- In order to record a new credit card it needs to be added as a new payment record. This is done by opening the booking and clicking on ‘Payments’.
- Record a new payment using payment method ‘DPS CAPTURE’ and hit Save.
- To add a new card, click on the ‘Payment Express’ logo, enter card data and hit Submit and Next.
- As you can see below, the Pay Ref (which is automatically provided by DPS). The iBex payment record for these transactions will show as "DPS Capture" for a zero amount. A Capture Payment record is always saved with both “hold” and “locked” status.
- The iBex payment record for these transactions will show as "DPS Capture" for a zero amount. A Capture Payment record is always saved with both “hold” and “locked” status.
- Card data stored via DPS Capture, will be tokenized and available for subsequent “DPS Charge” transactions.