Hosted Payment Page Options

Quick Find

Go straight to the section you need.

1.0 Gateway Integration →

1.1 Introduction

1.2 Terminology

1.3 Integration Methods

1.4 Integration Libraries

1.5 Security and Compliance

1.6 Prerequisites

1.7 Integration Details

1.8 Authentication

1.9 Supported Actions

2.0 New Transactions →

2.1 Request Fields

2.2 Response Fields

3.0 Management Requests →

3.1 Request Fields

3.2 Response Fields

4.0 AVS/CV2 Checking →

4.1 Background

4.2 Benefits and Limitations

4.3 Request Fields

4.4 Response Fields

5.0 3-D Secure Authentication →

5.1 Background

5.2 Benefits and Limitations

5.3 Hosted Implementation

5.4 Direct Implementation

5.5 Request Fields

5.6 Response Fields

5.7 Advanced Features

11 Receipts and Notifications →

11.1 Background

11.2 Customer Email Receipts

11.3 Request Fields

11.4 Response Fields

17 Advanced Data →

17.1 Customer Request Fields

17.2 Merchant Request Fields

17.3 Supplier Request Fields

17.4 Delivery Request Fields

17.5 Receiver Request Fields

17.6 Shipping Request Fields

17.7 Device Information Fields

 

19 Gateway Wallet → 

19.1 Background

19.2 Benefits and Limitation

19.3 Hosted

19.4 Direct Implentation

19.5 Request Fields

19.6 Response Fields

 

26 Digital Wallet Transactions →

26.1 Background

26.2 Benefits and Limitations

26.3 Configuration

26.4 Hosted Implementation

26.5 Direct Implementation

26.6 Request Fields

26.7 Response Fields

26.8 Digital Wallet Tokens

Appendix

A-1 Response Codes

A-1.1 Authorisation Response Codes

A-1.2 Gateway Response Codes

A-2 AVS / CV2 Check Response Codes

A-3 Secure Authentication Data

A-4 3-D Secure Enrolment/Authentication Only

A-9 Duplicate Transaction Checking

A-10 Capture Delay

A-11 Card Identification

A-12 Integration Testing

12.1 Test Amounts

12.2 Test Cards

12.3 3-D Secure Testing

 

A-13 Sample Signature Calculation

A-14 Transaction Life cycle

A-14.1 Authorise, Capture and Settlement

A-14.2 Transaction States

A-15 Transaction types

A-15.1 E-commerce (ECOM)

A-15.2 Mail Order/Telephone Order (MOTO)

A-15.3 Continuous Authority (CA)

 

A-16 Payment Tokenisation

A-16.1 PREAUTH, SALE, REFUND, VERIFY requests

A-16.2 REFUND_SALE requests

A-16.3 CANCEL or CAPTURE requests

A-16.4 QUERY requests

A-16.5 SALE or REFUND Referred Authorisation requests

 

A-18 PSD2 SCA Compliance

A-18.1 Obtaining Strong Customer Authentication

A-18.2 SCA Soft-Declines

A-18.3 Exemptions to Strong Customer Authentication

A-18.4 SCA Using 3-D Secure

 

A-19 Hosted Payment Page Options

A-20 Integration Libraries

A-20.1 Gateway Integration Library

A-20.2 Hosted Payment Page Library

A-20.3 Hosted Payment Fields Library

 

A-21 Example HTTP Requests

A-21.1 Hosted Integration

A-21.2 Direct Integration

A-21.3 Batch Integration

 

A-22 Example Integration Code

A-22.1 Hosted Integration

A-22.2 Direct Integration

A-22.3 Batch Integration

 

A-23 Example Library Code

A-23.1 Gateway Integration Library

A-23.2 Hosted Payment Page Library

A-23.3 Hosted Payment Fields Library

A-19 Hosted Payment Page Options

You can customise the appearance of the Hosted Payment Page by sending additional fields in the request. 

You can control which payment methods are displayed and the default or initial value to display in the input fields. 

You can also state which fields you require to be mandatory, in which case the payment form may not be submitted until the Cardholder has complete all the mandatory fields. On the standard modal Hosted Payment Page, the mandatory requirement can also control whether the field needs to be displayed. A value of ‘Y’ or ‘N’ means the field must be displayed, ‘Y’ indicates that a value must be supplied, while ‘N’ indicates the value can be blank. Omitting the request field means that the field need not be displayed if the form can provide a better user experience without it. 

Not all fields may be supported if you have a customised Hosted Payment Page

Field Name
cardNumber
Mandatory?
No1
Description
Default value for the Card number field.
Field Name
cardCVV
Mandatory?
No 2
Description
Default value for the Card security number field.
Field Name
cardExpiryMonth
Mandatory?
No
Description
Default value for the Card expiry month field.
Field Name
cardExpiryYear
Mandatory?
No
Description
Default value for the Card expiry year field.
Field Name
cardExpiryDate
Mandatory?
No
Description
Alternative to cardExpiryMonth/cardExpiryYear
Field Name
customerName
Mandatory?
No
Description
Default value for the Cardholder’s name field.
Field Name
customerAddress
Mandatory?
No
Description
Default value for the Cardholder’s address field.
Field Name
customerTown
Mandatory?
No
Description
Default value for the Cardholder’s town field.
Field Name
customerCounty
Mandatory?
No
Description
Default value for the Cardholder’s county field.
Field Name
customerPostcode
Mandatory?
No
Description
Default value for the Cardholder’s postcode field.
Field Name
customerCountryCode
Mandatory?
No
Description
Default value for the Cardholder’s country field.
Field Name
customerEmail
Mandatory?
No
Description
Default value for the Cardholder’s email field.
Field Name
customerPhone
Mandatory?
No
Description
Default value for the Cardholder’s phone number field.
Field Name
receiverDateOfBirth
Mandatory?
No
Description
Default value for the Cardholder’s date of birth field.
Field Name
cardCVVMandatory
Mandatory?
No
Description
Card security number field requirements (Y or N).
Field Name
customerNameMandatory
Mandatory?
No
Description
Cardholder’s name field requirements (Y or N).
Field Name
customerFullNameMandatory
Mandatory?
No3
Description
Cardholder’s name field requirements (Y or N).
Field Name
customerAddressMandatory
Mandatory?
No
Description
Cardholder’s address field requirements (Y or N).
Field Name
customerTownMandatory
Mandatory?
No
Description
Cardholder’s town field requirements (Y or N).
Field Name
customerCountyMandatory
Mandatory?
No
Description
Cardholder’s county field requirements (Y or N).
Field Name
customerPostcodeMandatory
Mandatory?
No
Description
Cardholder’s postcode field requirements (Y or N).
Field Name
customerCountryCodeMandatory
Mandatory?
No
Description
Cardholder’s country field requirements (Y or N).
Field Name
customerPostcodeMandatory
Mandatory?
No
Description
Cardholder’s postcode field requirements (Y or N).
Field Name
customerEmailMandatory
Mandatory?
No
Description
Cardholder’s email field requirements (Y or N).
Field Name
customerPhoneMandatory
Mandatory?
No
Description
Cardholder’s phone field requirements (Y or N).
Field Name
receiverDateOfBirthMandatory
Mandatory?
No
Description
Cardholder’s date of birth requirements (Y or N).
Field Name
formAmountEditable
Mandatory?
No
Description
Enables the payment amount to be edited by the consumer thus allowing the consumer to choose the amount they wish to pay.
Field Name
formResponsive
Mandatory?
No
Description
Request the Hosted Payment Page adjust its layout according to the browser display size etc. (Y or N).
Field Name
formAllowCancel
Mandatory?
No
Description
Request the Hosted Payment Page show a cancel button to allow the payment to be cancelled resulting in a transaction responseCode of 65576 (REQUEST CANCELLED).
Field Name
paymentMethod
Mandatory?
No
Description
Request the Hosted Payment Page invoke an alternative payment method on display without the need for the Customer to select it.
Field Name
allowedPaymentMethods
Mandatory?
No
Description
Comma separated list of paymentMethods supported by the Merchant to show on Hosted Payment Page where supported.
1 This should only be used by Merchants who are storing Card numbers as per PCI DSS requirements.
2 This should only be used for test purposed as Merchants are not allowed to store Card CVV numbers.
3 Same as customerNameMandatory only the name must be provided as at least two words of two or more characters.

Integrated Payments - connecting your till to your terminal

Integrated payments - connecting your EPOS till to your card terminal - enables your business to process payments faster and increase your profits.

There are many benefits to an integrated solution for almost all business types, most importantly, the removal of human error, giving you accurate reporting from all tills and terminals.

At Swipen, we offer Integrated Payments free of charge and you can use our Pay at Table or Pay at Counter software, or both if it suits your business:

Pay at Table

A software design with restaurants in mind:

Split the bill at the table

Automatic table closing

Integrated gratuity & reporting

Turn tables faster

More efficient payment

Pay at Counter

Suitable for most businesses, offering:

Faster payments

Shorter queues

Better conversion

Greater profits

COVID secure

Discover which terminal type is best for your business

Portable

Restaurants

Pubs

Cafes

Countertop

Bars

Clubs

Takeaways

Retail & Shops

Take your payments to the next level

E-Commerce Payment Solutions

With the arrival of Covid-19 into all our lives, online only payments are looking to have a bright future that’s here to stay.

At Swipen, we want to bust the myth that taking payments online is complicated, and help you
adapt to this changing world.

We offer two types of E-Commerce payment solution either directly integrated with your website or a hosted payment page.

Directly Integrated

Integrated into your own website

Completely customisable

Branded to your business

Customers stay on your website

150 currencies supported

Shopping carts

No long-term contract

Alternative payment methods, including: Alipay, Apple Pay, Google Pay, WeChatPay

Hosted Payment Page

Easy to set up

Take payments in minutes

Swipen branded

Data processed by Swipen

150 currencies supported

Shopping carts

No long-term contract

Alternative payment methods, including: Alipay, Apple Pay, Google Pay, WeChatPay

Take your payments to the next level

Virtual Terminal - Taking Payments over the Phone

Many businesses find it useful to take payments over the phone, whether you’re a travel agent
needing to take deposits, a mobile tradesperson, travelling salesperson, you have a call centre, or you don’t have a website to take payments online.

Swipen’s Virtual Terminal allows you to take card payments over the phone quickly and securely.

Our solution is a web portal that can be used on a desktop, tablet or mobile device.

Virtual Terminal Key Features

More secure than a card terminal - Completing the payment over the phone with full customer details reduces the risk of chargebacks or fraud.

Pay By Link - Send a payment link to complete the purchase or pay a balance. This is also a useful feature for customers who prefer to not give their details over the phone.

Capture Customer Details - The Virtual Terminal allows you to capture all the customer details you will need for your CRM or Booking Systems reducing the need for double inputting.

Control Permissions - Restrict user access to only certain functionality so you can control what your staff can process and see.

Take Payments anywhere - The Virtual Terminal is compatible to all devices and allows you to take payments from anywhere - office, home or on the move in a safe and secure way.

Ideal for call centres, travel agents, travelling salespeople, mobile tradespeople, restaurants for pre-bookings and parties, hotels for rooms and events, or any business that doesn’t have a website that customers can pay through.

Take your payments to the next level

Web & App Solutions - Order and Pay-at-Table Platform

With COVID regulations in force across the country, restaurants and pubs are adjusting the way they work to reduce the spread of this virus.

Swipen are also adapting to these changing times, and working with our expert partners, we can now offer order and pay-at-table platforms, allowing you to benefit from cashless and cardless payment options.

Our solutions can be either Web or App based and we provide the choice between
a ‘Simple Solution’ and a ‘Bespoke Solution’, depending on the size of your business

Bespoke Solution

The best option for individual pubs and restaurants, small chains, or if location offers a different menu:

Use your own branding

At table QR code or WiFi login

Bespoke rates and fees

Links to your EPOS till *

*Depending on the EPOS company

Simple Solution

Ideal for larger chains where every location requires exactly the same functionality and offers the same menu:

Custom built to fit your business

Customers can access the way you want

Links to both your till and kitchen

No training required

Working with Pizza Hut

Swipen have helped create a bespoke value-for money solution for Pizza Hut, and we could do the same for you.

Get in contact to find out more.

Take your payments to the next level

Tip Per Tap -Contactless Tipping System

With the dawn of cashless and touchless checkouts along with app ordering systems and pay online methods, many restaurants, bars, cafés and hotels are finding that their waiting staff are no longer able to receive cash or card tips.

Swipen has the perfect solution: the new ‘Tip Per Tap’ Contactless Tipping System

Directly Integrated

A dedicated terminal is placed in a prominent location in your restaurant.

The terminal is set to ‘donation’ and the debit amount is set at a specific figure. e.g. £2

Your happy customers simply tap their card, phone or watch against the terminal to leave a £2 tip.

They can tap multiple times to leave a larger amount

Works automatically without the need for a member of staff to supervise.

End-of-day report is separate, making it quicker and easier to share the total tips received between staff members.

How about a little Tip Per Tap

Read our blog all about our new Tip Per Tap Contactless Tipping System.

Get in contact to find out more.

Take your payments to the next level