An API to use the Worldpay Hosted Payment Pages (HPP) product.
An API to use the Worldpay Hosted Payment Pages (HPP) product.
The Transaction to create
A unique reference generated by you that is used to identify a payment throughout its lifecycle.
An object that contains information about the merchant.
An optional text, when supplied is displayed to your customer on payment pages.
The text that appears on your customer's statement. Used to identify the merchant.
An object containing the billing address information.
The payment amount.
The three character currency code. See list of supported currencies.
An object containing the different URLs we redirect your customers to when we receive the payment result. We recommend that you provide us with your custom result URLs.
When we receive the payment result for a successful payment, we redirect your customer to the success URL.
When we receive the payment result for a pending payment transaction, we redirect your customer to the pending URL.
When we receive the payment result for an erroneous payment, we redirect your customer to the error URL.
When your customer cancels a transaction, we redirect that customer to the cancel URL.
Data used for fraud and risk protection.
Allows you to configure the duration, in seconds, your customer can access the payment link.
An object that instructs us to create a token for the payment details supplied.
A namespace is used to group up to 16 cards, e.g. for one customer. A card can exist in more than one namespace.
A description of your token. If not supplied, a default description is created for you.
Used to choose how the customer could opt into their payment details being tokenized.
SILENT - (default value) The card details are always saved (you must already have their consent to do this)
NOTIFY - The card details are always saved (you must already have their consent to do this) and your customer will see this within our hosted payment pages
ASK - The card details are saved if your customer provides their consent. This adds a "Save payment details" tickbox to the page, which they tick to opt-in, or ignore to opt-out.
Contains specific customer agreements for the transaction. If this is present, then the creationToken must also be present
The processing arrangement agreed with your customer. Supported value:
cardOnFile
Add CSS options for each payment to customise the look and feel of the payment page.
Background color for the payment page in hex format. You can use three digit or six digit codes (e.g. #FFO or #DD99CC).
Text color for the payment page in hex format. You can use three digit or six digit codes (e.g. #FFO or #DD99CC).
Represents styling and customizations applied to the entire payment page, including colors, fonts, and borders.
An object containing 3DS authentication preferences, which can be used to turn 3DS off.
Create transaction request, all key:values
{ "transactionReference": "MyTransaction123", "merchant": { "entity": "POxxxxxxxxx" }, "narrative": { "line1": "Mind Palace Ltd" }, "value": { "currency": "GBP", "amount": 123 } }
Successful response
{ "url": "https://payments.worldpay.com/app/hpp/integration/transaction/xxxxxxxxxxxxxxxxxxxx&cs=yyyyyy" }