Alternative Payment Methods

Guide
Version 1.1 December 2012
Corporate Gateway

Table of Contents
About this Guide ........................................................................................................................ 3
Update History ....................................................................................................................... 3
Additional Documentation ...................................................................................................... 4
Copyright................................................................................................................................ 4
Overview of Alternative Payment Methods (APMs) .................................................................. 5
Understanding APM Transactions ......................................................................................... 6
XML Direct and Redirect Integration Models ......................................................................... 7
Payment Service Providers.................................................................................................... 8
Default and Supported Languages ........................................................................................ 9
Acceptance Currency, Preferred Currency, and Settlement Currency................................ 11
Maximum and Minimum Transaction Limits ........................................................................ 12
Payment Statuses and Delays............................................................................................. 13
Chargebacks ........................................................................................................................ 14
APM Categories and Payment Messaging Flows ................................................................... 15
Characteristics and Categories of APMs ............................................................................. 15
Direct Model: Payment Messaging Flow ............................................................................. 17
Redirect Model: Payment Messaging Flow ......................................................................... 18
1. Submitting an XML Order Request.................................................................................. 19
2. Redirecting the Shopper to Payment Pages.................................................................... 21
3. Accepting the Payment and Displaying the Result Page ................................................ 22
4. Capturing the Payment and Notifying the Shopper ......................................................... 30
Supported APMs and Example XML Orders........................................................................... 31
Supported APMs.................................................................................................................. 31
Real-Time Hybrid APMs ...................................................................................................... 32
Delayed Hybrid APMs.......................................................................................................... 91
Real-Time Non-Hybrid APMs............................................................................................. 126
Delayed Non-Hybrid APMs ................................................................................................ 136
About Testing APM Transactions .......................................................................................... 140
About Refunding Payments................................................................................................... 141

Alternative Payment Methods Guide

Scope ................................................................................................................................. 141
Fraud and Risk Management............................................................................................. 141
Tracking and Audit Control ................................................................................................ 141
APM Quick Reference ........................................................................................................... 143
Real-Time Hybrid Payment Methods................................................................................. 143
Delayed Hybrid Payment Methods .................................................................................... 151
Real-Time Non-Hybrid Payment Methods ......................................................................... 154
Delayed Non-Hybrid Payment Methods ............................................................................ 156

ii

About this Guide

This guide explains how to use the WorldPay Payment Service to accept and process
payments that are made using Alternative Payment Methods (APMs), and provides the
following information:
Overview of concepts related to APMs.
Features that affect payment transactions and the shopper experience.
Various categories of APMs and the APM payment messaging flows in the XML
direct and redirect models.
Detailed information including the payment method properties and example XML
orders for supported APMs.
Read this guide in conjunction with the following guides:
Submitting Transactions in the XML Direct Model Guide.
Hosted Payment Page (XML Redirect) Guide.
This guide assumes that you have basic XML knowledge and are familiar with using the XML
direct and redirect integration models to integrate with the WorldPay Payment Service.

This guide only includes the APMs that are supported by WorldPay AP Limited. For
information about other APMs such as PayPal and iDeal, see the following guides:

Submitting Transactions in the XML Direct Model Guide.

Hosted Payment Page (XML Redirect) Guide.

Update History
Version

Date

Change Description

1.1

December 2012

Minor fixes.

1.0

November 2012

New guide for APMs supported by WorldPay AP Ltd.

Alternative Payment Methods Guide

Additional Documentation
Guide

Description

Document Type Definition

for XML Integration

Defines the rules for structuring XML order requests that

you submit to the WorldPay Payment Service for
processing.

Hosted Payment Page (XML

Redirect) Guide

Provides the specification for XML order requests and

explains how to submit these requests in the redirect
integration model.

Merchant Interface User

Guide

Explains how to administer your WorldPay Payment Service

account by using the Merchant Interface (MI).

Order Modifications and

Order Inquiries Guide

Explains how to cancel, capture, or refund an order

payment by submitting XML order modifications.

Order Notifications Reporting Payment Statuses

Guide

Explains how to use order notifications to report status

changes for payments.

Refunding Alternative
Payments Guide

Explains how to refund payments that were made by using

alternative payment methods.

Sandbox User Guide

Explains how to test the payment cycle for APMs by using

the Sandbox system.

Submitting Transactions in
the XML Direct Model Guide

Provides the specification for XML order requests and

explains how to submit these requests in the direct
integration model.

Copyright
WorldPay (UK) Limited
While every effort has been made to ensure the accuracy of the information contained in this
publication, the information is supplied without representation or warranty of any kind, is
subject to change without notice and does not represent a commitment on the part of
WorldPay (UK) Limited. WorldPay (UK) Limited, therefore, assumes no responsibility and
shall have no liability, consequential or otherwise, of any kind arising from this material or any
part thereof, or any supplementary materials subsequently issued by WorldPay (UK) Limited.
WorldPay (UK) Limited has made every effort to ensure the accuracy of this material.

Overview of Alternative Payment Methods (APMs)

Overview of Alternative Payment Methods (APMs)

In many countries, traditional card-based payment methods are not the principal means by
which shoppers pay for goods and services. Card-based payment methods have many
disadvantages and limitations, including the following:
Shoppers often do not prefer to disclose their card details to third parties.
Many shoppers, for example those without bank accounts, do not have access to
debit or credit cards. These shoppers therefore cannot use card-based payment
methods to purchase goods and services.
Although card-based payment methods are common in many countries, there are not
used in many other countries due to cultural preferences and practical reasons.
In many countries, cash is still the most popular payment method.
These limitations are reduced by the use of Alternative Payment Methods (APMs). The
WorldPay Payment Service considers an APM as any method that is not one of the globally
recognised credit or debit card brands, and includes the following types of payments:
eWallets, for example Yandex.Money and WebMoney.
Offline bank transfers.
Pre-pay cards and vouchers, for example Ticket Premium and Swiff.
Post-pay vouchers, for example Boleto.
Real-time bank transfers, for example PlusPay.
Local payment cards, for example Paga Verve.
APMs are offered by branded Payment Service Providers (PSPs) and are used worldwide in
a variety of sectors. Shoppers can use APMs to purchase goods and services from different
geographic locations. As a merchant, you can use APMs to trade globally and engage with
shoppers worldwide, ensure a smooth payment process, and increase your sales and
revenue.
This guide explains how to accept and process APM payments by using the WorldPay
Payment Service.

Alternative Payment Methods Guide

Understanding APM Transactions

A typical APM payment transaction involves a number of entities and components including
the merchant website, WorldPay Payment Service, and PSP.
The following figure shows the entities involved in a payment transaction, the flow for a
payment made with an APM, and the various features that affect payment transactions and
the shopper experience.

Figure 1: Alternative Payment Transaction Flow

Overview of Alternative Payment Methods (APMs)

XML Direct and Redirect Integration Models

You can process APM payments by submitting XML orders to the WorldPay Payment
Service, using either the direct or redirect integration model. The features of these models
are summarised in the following table.

Model

Features
You can submit the order and payment details directly to the WorldPay
Payment Service. With the direct method, the shopper selects the payment
method and provides mandatory data to you before you submit this
information to WorldPay. You can also specify your website URLs to which
the shoppers must be redirected after they complete the payment.

Direct
integration

This model is suitable if:

You are an existing merchant who already uses the direct model.
You want to manage the shopper data and more of the of the shopper
journey, within your own environment.
For more information about submitting orders in the direct model, see
Submitting Transactions in the XML Direct Model Guide.
You can redirect shoppers from your website to the WorldPay payment
pages to complete the payment. Shoppers select the payment method and
type additional mandatory data on the WorldPay payment pages. WorldPay
is responsible for:
Validating the data entered by the shopper.
Ensuring that the data is held and disposed securely.

Redirect
integration

This model is suitable if you want to accept a mix of card and APM
payments, without adding complexity (such as handling payment data) to
your own systems. If you are an existing redirect merchant, new payment
methods may be added to your hosted payment page without the need to
change your incoming message. You can also incorporate the latest APM
releases with no or minimal development effort.
With the redirect model, you can also choose to:
Specify your website URLs to which the shoppers must be redirected after
they complete the payment.
Customise the WorldPay payment pages to match your website, to ensure
that your website and the WorldPay payment pages have a consistent look
and feel.
Dynamically control the range of payment methods that you want to offer to
the shopper.
For more information about creating and submitting XML orders in the
redirect model, see Hosted Payment Page (XML Redirect) Guide.

For information about how APM payments are processed in the direct and redirect models,
see APM Categories and Payment Messaging Flows.
7

Alternative Payment Methods Guide

For information about submitting orders to process payments that are made by using specific
APMs, see Supported APMs and Example XML Orders.

Payment Service Providers

When a shopper makes a payment, the shopper data is sent to the appropriate Payment
Service Provider (PSP) for validation and authorisation. Depending on the payment method
used, if the shopper data is valid, the PSP either:
Authorises the payment, without prompting the shopper for any further information.
The payment pages of the PSP therefore remain invisible to the shopper.
Prompts the user to perform additional tasks to complete the payment. For example,
if a shopper makes a payment by using bank transfer, the PSP prompts the shopper
to choose their online bank and proceed with the payment.
After the PSP confirms the outcome of the payment to WorldPay, the WorldPay Payment
Service returns the result of the transaction to you.

Throughout this guide, the term Payment Service Provider refers to the service
providers of APM and not WorldPay.
In some scenarios, the same PSP might be associated with several APMs. For
example, DineroMail is the PSP for the following APMs:

DineroMail 7eleven

DineroMail OXXO

DineroMail Offline Bank Transfer

Overview of Alternative Payment Methods (APMs)

Default and Supported Languages

The WorldPay Payment Service supports a number of languages. PSPs commonly support
only a subset of the languages offered by the WorldPay Payment Service. The default
language for an APM is one of the supported languages.
For information about the default and supported languages for individual payment methods,
see Supported APMs and Example XML Orders.

Direct Model
In the direct model, the PSP pages are always displayed in the default language associated
with the APM.

Redirect Model
In the redirect model, the shopper chooses to view the payment pages in any language
supported by the WorldPay Payment Service. If the language is supported by the PSP, the
WorldPay payment pages and the PSP payment pages are displayed in the language
selected by the shopper.
If the language is not supported by the PSP, the PSP payment pages are displayed in the
default language, as shown in the following figure.

Figure 2: Default and Supported Languages in the Redirect Model

In the above example, if a shopper wants to use the DineroMail 7eleven payment method
and chooses to view the payment pages in French:
Because French is a language that is supported by the WorldPay Payment Service,
the WorldPay payment pages are displayed in French.
The PSP pages are displayed in English, which is the default language for the
DineroMail 7eleven payment method.

Alternative Payment Methods Guide

Languages Supported by the WorldPay Payment Service

The languages that are supported by the WorldPay Payment Service are listed in the
following table.
Language

Language Code

Bosnian

bs

Bulgarian

bg

Chinese

zh

Croatian

hr

Czech

cs

Danish

da

Dutch

nl

English

en

Estonian

et

Finnish

fi

French

fr

German

de

Greek

el

Hungarian

hu

Italian

it

Japanese

ja

Korean

ko

Latvian

lv

Norwegian

no

Polish

pl

10

Overview of Alternative Payment Methods (APMs)

Portuguese

pt

Romanian

ro

Russian

ru

Sinhalese

si

Slovak

sk

Spanish

es

Swedish

sv

Turkish

tr

Acceptance Currency, Preferred Currency, and

Settlement Currency
An APM has one or more acceptance currencies in which the payment is authorised. For
example, if a shopper makes a payment by using the SafetyPay payment method, the
payment is authorised in either USD or EUR.

Preferred Currency
To manage payments that are not made with an acceptance currency, each APM also has a
preferred currency. If a shopper makes a payment in a different currency to the acceptance
currency, the amount is converted to the preferred currency, as shown in the following figure.

Figure 3: Currency Conversion

As shown in the above example, if a shopper makes a payment in JPY when using the
SafetyPay payment method, the payment is converted to EUR, which is the preferred
currency for SafetyPay.

11

Alternative Payment Methods Guide

WorldPay Settlement Currency and Merchant Settlement

Currency
After a payment is authorised, the PSP settles the payment to WorldPay in the WorldPay
settlement currency. WorldPay then settles the currency to you in the merchant settlement
currency. The merchant settlement currency is specified in your contract.
For information about the authorisation, preferred, and settlement currencies for individual
APMs, see Supported APMs and Example XML Orders.

Maximum and Minimum Transaction Limits

The WorldPay transaction limits determine the maximum and minimum amount that a
shopper can pay in a single transaction. The WorldPay transaction limit is always imposed in
a single currency, which is also known as the limit currency. During authorisation, the limit is
checked by converting the payment amount to the limit currency.
Additionally, the PSP may impose its own maximum and minimum transaction limits. These
limits may periodically differ from the transaction limits imposed by WorldPay.
If the amount is higher than the maximum transaction limit or lower than the minimum
transaction limit:
For payments made in the direct model, the WorldPay Payment Service returns an
error.
For payments made in the redirect model, the payment method is not displayed on
the WorldPay payment pages.
We recommend that you validate your orders to ensure that you do not request authorisation
of payments for amounts that are higher than the maximum transaction limit or lower than the
minimum transaction limit.

The maximum and minimum transaction limits can change from time to time. We
recommend that you periodically check the WorldPay transaction limits to ensure
that the payment transactions are within the transaction limits.

For the maximum and minimum amounts supported on each APM, see the APM Quick
Reference.

12

Overview of Alternative Payment Methods (APMs)

Payment Statuses and Delays

After a shopper makes a payment, you can track the status of the payment by using the
Merchant Interface (MI). The various APM statuses are described in the following table.

Status

Description
Direct model: The shopper has selected a payment
method and made the payment.

SHOPPER_REDIRECTED

Redirect model: The order is created and the

shopper has selected the required payment method
and provided any additional payment information on
the WorldPay website.

AUTHORISED

The PSP has authorised the payment.

CAPTURED

The WorldPay Payment Service has received the pay-in

notification and the payment from the PSP.

SETTLED

The WorldPay Payment Service has settled the payment to

you.

Depending on your account set up, you might receive email notifications from the WorldPay
Payment Service that inform you about the changes in the payment status. For more
information about configuring the WorldPay Payment Service to send notifications, see the
Order Notifications - Reporting Payment Statuses Guide.

Payment Delays
The type of APM used to make a payment determines the delay from the time the shopper
makes their payment to the time the payment status changes to SETTLED.
With delayed APMs, the status continues to show SHOPPER_REDIRECTED for a period of
time, for example, if there is a delay with the shopper making the payment and also a delay in
the PSP authorising the payment.

Because the payment to the PSP occurs outside the WorldPay Payment Service, the
payment delay varies depending on the PSP being used.

13

Alternative Payment Methods Guide

Chargebacks
Chargebacks are supported by a subset of APMs, where a shopper can request the PSP to
reverse the payment transaction. Examples of scenarios when a shopper can request a
chargeback include:
The shopper has not received the goods or services.
The shopper has received goods or services that are not as described.
The shopper has not made the purchase, but has been charged because their
payment system, for example an eWallet has been used fraudulently.
If the PSP accepts the chargeback, the WorldPay Payment Service reverses the payment.
You can view all chargebacks by using the Merchant Interface. For more information about
chargebacks, contact WorldPay Support.
For information about chargebacks related to specific APMs, see Supported APMs and
Example XML Orders.

There is no dispute process for chargebacks that result from APMs.

14

APM Categories and Payment Messaging Flows

When a shopper makes a payment, the WorldPay Payment Service sends the payment
request to the PSP for authorisation. The PSP receives the payment request, validates the
data, and then initiates the necessary actions to proceed with the payment. The payment
processing varies depending on the type of APM used by the shopper and the integration
model that you use to connect to the WorldPay Payment Service.
This section describes:
The characteristics of the APMs supported by WorldPay and categorises the APMs
based on these characteristics.
The payment messaging flows for each category of APMs.

Characteristics and Categories of APMs

The characteristics of the APMs supported by the WorldPay Payment Service are listed in the
following table.

Payment
Category

Description

The payment is authorised in real-time during the shopper payment journey.

Real-time
APMs

After the PSP has authorised the payment and WorldPay has received the
pay-in notification, the payment status on the MI changes from
SHOPPER_REDIRECTED to AUTHORISED, and you receive notification of
the successful payment.
There is a delay from the end of the shopper payment journey to the
payment being authorised. The payment continues to remain in the
SHOPPER_REDIRECTED status for hours or days, depending on the
payment method used.
The payment delay can result from number of factors such as:

Delayed
APMs

The shopper cannot complete the entire payment immediately. For

example, if the shopper uses a voucher payment method, they might
have to withdraw cash and settle the voucher at an outlet.

The PSP receives notification from the outlet at which the shopper
makes the payment a few hours after the payment has been made.

The online bank at which the shopper makes the payment can only
authorise payments during working hours.

After the PSP has authorised the payment and WorldPay has received the
pay-in notification, the payment status on the MI changes from
SHOPPER_REDIRECTED to AUTHORISED, and you receive notification of
the successful payment.
Hybrid
APMs

When using hybrid payment methods, shoppers might have to interact

directly with the PSP or bank during the shopper payment journey.

15

Alternative Payment Methods Guide

For example, when using a hybrid payment method, the shopper might have
to:

Provide their eWallet credentials on the PSP website to approve an

eWallet payment.

Print out and pay a voucher.

Hybrid payment methods can be either real-time or delayed.

Non-hybrid payment methods do not require any direct interaction between
the shopper and the PSP or bank. All activity is self-contained within your
website or the WorldPay payment pages.

Non-Hybrid
APMs

For example, for a pre-pay voucher method, where the shopper has a
unique code representing a monetary value, the shopper can do one of the
following for a non-hybrid method:

In the direct model, type the code on your website.

In the redirect model, type the code on the WorldPay payment pages.

Non-hybrid payment methods can be either real-time or delayed.

APM Categories
Based on their characteristics, APMs are categorised as shown in the following table.

Real-time

Delayed

Hybrid

Real-time hybrid APMs

Delayed hybrid APMs

Non-hybrid

Real-time non-hybrid
APMs

Delayed non-hybrid APMs

About Shipping your Goods or Services

We recommend that you:
Use APMs that are suitable for your business. For example, if you are selling
perishable goods or services, you might require the payment authorisation
notification within hours. However, with some delayed APMs, the payment may not
be authorised for a few days.
Ship your goods only after the payment is authorised and the payment status on the
MI changes to either AUTHORISED or CAPTURED. The payment is transferred into
your account after the status on the MI changes to SETTLED.
For information about the anticipated delay for various APMs, see Supported APMs and
Example XML Orders.

16

APM Categories and Payment Messaging Flows

To optimise the shopper and merchant experience, you can also include text on your
website, requesting that shoppers who use delayed methods complete their payment
within a given time period.

Direct Model: Payment Messaging Flow

When a shopper makes a payment by using an APM, the payment is processed in stages,
depending on:
The model that you use to integrate with the WorldPay Payment Service.
The category of APM that the shopper uses to make the payment.
In the direct model, the shopper selects the payment method and provides mandatory data to
you before you submit this information to WorldPay. You can also specify your website URLs
to which the shoppers must be redirected after they complete the payment.
The following figure shows the payment messaging flow for APM payments that are made in
the direct model.

Figure 4: APM Payment Messaging Flow in the Direct Model

For details of the various stages involved in the process, see the following topics:
17

Alternative Payment Methods Guide

1. Submitting an XML Order Request.
2. Redirecting the Shopper to Payment Pages.
3. Accepting the Payment and Displaying the Result Page.
4. Capturing the Payment and Notifying the Shopper.

Redirect Model: Payment Messaging Flow

When a shopper makes a payment by using an APM, the payment is processed in stages,
depending on:
The model that you use to integrate with the WorldPay Payment Service.
The category of APM that the shopper uses to make the payment.
In the redirect model, you can redirect shoppers from your website to the WorldPay payment
pages to complete the payment. Shoppers can select the payment method and provide
additional mandatory data on the WorldPay payment pages. WorldPay is responsible for
validating shopper data and ensuring that the data is held and disposed of securely.
The following figure shows the payment messaging flow for APM payments that are made in
the redirect model.

Figure 5: APM Payment Messaging Flow in the Redirect Model

18

APM Categories and Payment Messaging Flows

For details of the various stages involved in the process, see the following topics:
1. Submitting an XML Order Request.
2. Redirecting the Shopper to Payment Pages.
3. Accepting the Payment and Displaying the Result Page.
4. Capturing the Payment and Notifying the Shopper.

1. Submitting an XML Order Request

To process a shopper payment, you must first submit an XML order request containing the
order and payment information listed in the following table.

Information

Description
Provide the following order details:

Order
details

Description of the order.

Order amount, currency code, value, and exponent.

For detailed information about the order details that you must submit,
see:

Submitting Transactions in the XML Direct Model Guide.

Hosted Payment Page (XML Redirect) Guide.

Provide the following payment details:

The payment method mask for the APM being used to make the
payment.

Direct model: The order must contain only one payment

method mask.

Redirect model: The order can contain multiple

payment method masks.

For a list of payment method masks, see the APM Quick Reference.
Payment
details

Direct model only: The following URLs to which the shopper

must be redirected after the payment is complete:

successURL: The URL that is returned if the payment is

authorised successfully in real-time. This URL is
returned for real-time payment methods.

cancelURL: The URL that is returned if the payment is

cancelled.

pendingURL: The URL that is returned if the payment is

neither authorised in real-time nor cancelled. This URL is
returned for delayed payment methods.

19

Alternative Payment Methods Guide

Note: In the redirect model, you do not have to include these URLs in the
order. You must append them to the response returned by the WorldPay
Payment Service.

The statementNarrative element, which includes the text that

must be displayed on the shopper's statement.

Note: The statementNarrative element is currently supported by the

Qiwi and AliPay payment methods only.

Shopper
details

Direct model: Provide the mandatory shopper details.

Redirect model: We recommend that you provide the mandatory

shopper details, if the details are available.

The mandatory details that you must supply vary depending on the APM
being used. For information about the mandatory details that you must
include for individual APMs, see Supported APMs and Example XML
Orders.

After you submit an order:

Direct model: The WorldPay Payment Service creates an order and a payment
request simultaneously by extracting the order and payment details from the XML
order that you submit.
Redirect model: The shopper selects the payment method on the WorldPay
payment pages. The WorldPay Payment Service might also capture additional
payment-method specific parameters such as the address and telephone number
that the shopper provides on the payment pages. The WorldPay Payment Service
then:
Creates an order at the point that you successfully submit your order.
Creates a payment request after the shopper has selected the required
payment method and provided any additional payment information.
The payment request is created in the SHOPPER_REDIRECTED status.
For example XML orders and the mandatory data that you must include in your order for
individual APMs, see Supported APMs and Example XML Orders.

20

APM Categories and Payment Messaging Flows

2. Redirecting the Shopper to Payment Pages

After the request is accepted, the WorldPay Payment Service typically returns an XML
response of the following form:
http://www.worldpay.com/successURL?orderKey=BIBIT^DEMO^Example_Tod
itoCash_Order&paymentStatus=AUTHORISED&paymentAmount=100
&paymentCurrency=USD&mac=24dcd933111a50e0f29c32f4d78ad62a
The response includes various components, which are described in the following table.

Components

Description

http://www.worldpay.com/successU
RL

The successURL that you have specified in your

XML order request.*
The orderKey parameter, including:

orderKey=BIBIT^DEMO^Example_
ToditoCash_Order

The admin code, with the limiter (^)

appended. This value can be null.

The merchant code, with the limiter (^)

appended*.

The order code specified in the original

XML order request*.

paymentStatus=AUTHORISED

The status of the payment*.

paymentAmount=100

The amount of the payment*.

paymentCurrency=USD

The currency of the payment*.

The MAC secret. This value can be null if the
MAC secret is not used.
Note: The MAC is returned if all the following conditions
are met:

mac=24dcd933111a50e0f29c32f4d
78ad62a

The MAC secret is ENABLED.

The MAC secret was previously changed from
DISABLED to ENABLED.
The payment is in the AUTHORISED,
REFUSED, CANCELLED, or CAPTURED
status.

* This value cannot be null.

If you are using the direct model, redirect the shopper to this URL, so that the shopper can
complete the next steps in the payment process.

21

Alternative Payment Methods Guide

If you are using the redirect model, append the following details to the URL, before
redirecting the shopper:
The country and language code for the shopper.
The success URL, cancel URL, and pending URL for the transaction.
For more information about redirecting shoppers, see Submitting Transactions in the XML
Direct Model Guide.
At the end of this stage:
Direct model: The WorldPay Payment Service sends the payment request to the
PSP for validation.
Redirect model: The shopper is redirected to the WorldPay payment pages to
complete the next steps in the payment process.

3. Accepting the Payment and Displaying the Result

Page
When the PSP receives the payment request and validates the data, it initiates the necessary
steps to complete the payment depending on the type of payment method used:
Non-hybrid payment methods: The PSP completes the payment without requesting
the shopper to provide any further information. The PSP pages therefore remain
invisible to the shopper.
Hybrid payment methods: These payment methods require further interaction
between the PSP and the shopper. For example, if the shopper uses a post-pay
voucher, they may have to print out a voucher from the PSP's website and make the
payment at an outlet.
For more information about how the payment is processed for different categories of APMs,
see PSP Payment Processing Scenarios.
When the payment is complete, the PSP confirms the result of the payment and initiates the
pay-in process to the WorldPay Payment Service. The WorldPay Payment Service then
returns a result URL based on the current status of the payment within the system.
The possible result URLs are described in the following table.

Result URL

Description

Payment Status on the

MI

This URL is returned if the WorldPay

Payment Service has received the pay-in
notification from the PSP and has
authorised the payment.
successURL

AUTHORISED
This URL is commonly returned for realtime payment methods, if the PSP accepts
the payment request.

22

APM Categories and Payment Messaging Flows

cancelURL

This URL is often returned if the payment

has been cancelled by the shopper on the
PSP pages.

SHOPPER_CANCELLED

Note: Some PSPs do not provide a

Cancel button on their Website.

pendingURL

This URL is returned if the payment is

neither authorised in real-time nor
cancelled. This URL is commonly returned
for delayed payment methods.

SHOPPER_REDIRECTED

In some cases, shoppers might complete the payment, but not the entire payment
journey. For example, a shopper might close the browser before the successURL is
returned. We therefore strongly recommend that you only use the result URLs to
redirect shoppers to the result. Do not use these URLs to update your order details.
Ensure that you use order notifications to update the status of your orders. For more
information, see the Order Notifications - Reporting Payment Statuses Guide.

After the payment is authorised, display the URL to the shopper.

PSP Payment Processing Scenarios

When the PSP receives a payment request, it initiates the necessary steps to complete the
payment. These steps vary depending on the type of payment method used. This section
explains the PSP payment process for the following categories of APMs:
Real-time hybrid APMs.
Delayed hybrid APMs.
Real-time non-hybrid APMs.
Delayed non-hybrid APMs.

Real-Time Hybrid APMs

When using hybrid payment methods, shoppers might have to interact directly with the PSP
or financial institution during the shopper payment journey. For example, when using a hybrid
payment method, the shopper might have to:

Provide their eWallet credentials on the PSP website to approve an eWallet payment.

Log in to the website of their bank and provide their bank credentials.

Payments that are made using real-time hybrid APMs are commonly authorised immediately
during the shopper payment journey.

23

Alternative Payment Methods Guide

The PSP payment process for real-time hybrid APMs is shown in the following figure.

Figure 6: PSP Payment Process for Real-Time Hybrid APMs

The PSP receives the payment request, validates the data, and initiates the necessary steps
for the shopper to make the payment. For example, the PSP might prompt the shopper to
provide their eWallet credentials.
After the payment is authorised and the WorldPay Payment Service receives the pay-in
notification, the payment status on your MI changes from SHOPPER_REDIRECTED to
AUTHORISED. The WorldPay Payment Service then notifies you about the successful
payment.

24

APM Categories and Payment Messaging Flows

Delayed Hybrid APMs

When using hybrid payment methods, shoppers might have to interact directly with the PSP
or financial institution during the shopper payment journey. For example, when using a hybrid
payment method, the shopper might have to:

Print out and pay a voucher.

Record the beneficiary details shown on the screen and complete a payment through
their bank.

With delayed hybrid APMs, there is a delay from the end of the shopper payment journey to
the payment being authorised. Depending on the payment method used, the payment may
remain in the SHOPPER_REDIRECTED status for a number of hours or days. The payment
delay can result from number of factors such as:

The payment involves additional actions that must be completed offline. For example,
if the shopper uses a voucher payment method, they might have to withdraw cash
and settle the voucher at an outlet.

The PSP receives notification from the outlet at which the shopper makes the
payment a few hours after the payment has been made.

The online bank at which the shopper makes the payment can only authorise
payments during working hours.

25

Alternative Payment Methods Guide

The PSP payment process for delayed hybrid APMs is shown in the following figure.

Figure 7: PSP Payment Process for Delayed Hybrid APMs

The payment status on the MI continues to show SHOPPER_REDIRECTED and the shopper
is redirected to the pending URL.
After the shopper completes the additional payment steps offline, the PSP authorises the
payment and sends a pay-in notification to WorldPay. The WorldPay Payment Service
receives the pay-in notification, after which the payment status on your MI changes from
SHOPPER_REDIRECTED to AUTHORISED. The WorldPay Payment Service then notifies
you about the successful payment.

26

APM Categories and Payment Messaging Flows

Real-Time Non-Hybrid APMs

Non-hybrid payment methods do not require any direct interaction between the shopper and
the PSP or financial institution. All activity is self-contained within your website or the
WorldPay payment pages.
For example, for a pre-pay voucher method, where the shopper has a unique code
representing a monetary value, the shopper can do one of the following:

In the direct model, type the code on your website.

In the redirect model, type the code on the WorldPay payment pages.

Payments that are made using real-time non-hybrid APMs are authorised immediately during
the shopper payment journey.
The PSP payment process for real-time non-hybrid APMs is shown in the following figure.

Figure 8: PSP Payment Process for Real-Time Non-Hybrid APMs

27

Alternative Payment Methods Guide

The PSP receives the payment request, validates the data, and completes the payment
without any additional shopper interaction. If the payment is successful, the payment status
changes from SHOPPER_REDIRECTED to AUTHORISED. The shopper is then redirected
to the success URL.

Delayed Non-Hybrid APMs

Non-hybrid payment methods do not require any direct interaction between the shopper and
the PSP or financial institution. All activity is self-contained within your website or the
WorldPay payment pages.
For example, for the Multibanco payment method, where the shopper has a unique code
representing a monetary value, the shopper can do one of the following:

In the direct model, type the code on your website.

In the redirect model, type the code on the WorldPay payment pages.

With delayed non-hybrid APMs, there is a delay from the end of the shopper payment journey
to the payment being authorised. Depending on the payment method used, the payment
remains in the SHOPPER_REDIRECTED status for a number of hours or days.
The payment delay can result from number of factors such as:

The payment involves additional actions that must be completed offline. For example,
if the shopper uses a voucher payment method, they might have to withdraw cash
and settle the voucher at an outlet.

The PSP receive notification from the outlet at which the shopper makes the payment
a few hours after the payment has been made.

The online bank at which the shopper makes the payment can only authorise
payments during working hours.

28

APM Categories and Payment Messaging Flows

The PSP payment process for delayed non-hybrid APMs is shown in the following figure.

Figure 9: PSP Payment Process for Delayed Non-Hybrid APMs

The payment status on the MI continues to show SHOPPER_REDIRECTED and the shopper
is redirected to the pending URL.
After the shopper completes the additional payment steps, the PSP authorises the payment
and sends a pay-in notification to WorldPay. The WorldPay Payment Service receives the
pay-in notification, after which the payment status on your MI changes from
SHOPPER_REDIRECTED to AUTHORISED. The WorldPay Payment Service then notifies
you about the successful payment.

29

Alternative Payment Methods Guide

4. Capturing the Payment and Notifying the Shopper

When the WorldPay Payment Service receives the pay-in notification from the PSP, the
payment status on the MI changes to AUTHORISED. The WorldPay Payment Service then
sends an authorisation notification to you.
For real-time payment methods, you receive the authorisation notification in real-time. For
delayed payment methods, the authorisation notification is not issued immediately. For
information about the delays you can expect with individual APMs, see Supported APMs and
Example XML Orders.
After you receive the authorisation notification, you can:
Process the authorisation notification and send an email to the shopper to confirm
the receipt of payment.
Ship your goods or services to the shopper.

30

Supported APMs and Example XML Orders

Supported APMs
Before you begin, ensure that you:

Read the APM related concepts explained in Overview of Alternative

Payment Methods.

Familiarise yourself with the categories of APMs and the payment flows
described in APM Categories and Payment Messaging Flows.

This section provides the descriptions, payment method properties, and example XML orders
for APMs belonging to the following categories:
Real-time Hybrid APMs.
Delayed Hybrid APMs.
Real-time Non-Hybrid APMs.
Delayed Non-Hybrid APMs.
All APMs are supported on both direct and redirect models.

About Refunding Payments

All payments made by using APMs can be refunded within 60 days from the date the
payment was authorised. Depending on your business requirements, you can:
Refund a payment either partially or completely.
Refund a payment directly to the original payment medium, for example, into an
eWallet, offered by the PSP. The automated PSP refund option is currently available
only for a subset of APMs.
Refund a payment manually by making a bank transfer, for example, if the original
payment method does not support automated PSP refunds or if attempts to refund a
payment by the automated PSP refund option have failed.
For more information about refunding payments, see the Refunding Alternative Payments
Guide.

31

Alternative Payment Methods Guide

About Shipping your Goods or Services

We recommend that you:
Use APMs that are suitable for your business. For example, if you are selling
perishable goods or services, you might require the payment authorisation
notification within hours. However, with some delayed APMs, the payment may not
be authorised for a few days.
Ship your goods only after the payment is authorised and the payment status on the
MI changes to either AUTHORISED or CAPTURED. The payment is transferred into
your account after the status on the MI changes to SETTLED.
To optimise the shopper and merchant experience, you can also include text on your
website, requesting that shoppers who use delayed methods complete their payment
within a given time period.

Real-Time Hybrid APMs

When using a real-time hybrid payment method, shoppers must complete additional tasks or
interface with the PSP to complete the payment. When a shopper makes a payment by using
a real-time hybrid method, the payment is authorised in real-time and you receive immediate
notification.

99Bill
99Bill is a payments aggregator in China that supports the following payment methods:
eWallet payment.
Internet banking payment.
Telephone payment.
Corporate banking online payment.
Credit card payment.
Mobile phone payment.
The WorldPay Payment Service supports the Internet banking payment option. Shoppers can
use this option to make payments directly from their online bank account by using one of the
following methods, depending on their banking policy:
Bank transfer.
Debit, credit, and corporate cards.
Quasi credit card, which requires the shopper to maintain a deposit or bank balance.
Passbook.
eCard.
To make a payment by using this method:

32

About Testing the Integration

1. On the payment page, the shopper selects the 99Bill payment method. The shopper
is redirected to the 99Bill website.
2. The shopper selects the required bank from which the payment must be made. The
shopper is redirected to the website of the bank.
3. The shopper logs on to the bank, and then makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Internet banking

Country

China

Default Language

zh

Supported Language

zh

Acceptance Currency

CNY

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 CNY

Maximum Amount for a Single

Transaction

750 CNY

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

NINETYNINEBILL-SSL

statementNarrative (Yes/No)

No

33

Alternative Payment Methods Guide

Payment Delays and Status Changes
After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Shopper chooses the

payment method.

Delay

Payment Status

Notes

SHOPPER_
REDIRECTED

The payment is
created in the
SHOPPER_REDIRE
CTED status.

Shopper makes the

payment.

X
minutes

SHOPPER_REDIR
ECTED

The shopper must

make the payment
within five days. The
bank might
conditionally process
the payment after this
period.

PSP authorises the

payment.

AUTHORISED

The WorldPay
Payment Service
captures the payment.

Less
than 1
hour

CAPTURED

The WorldPay
Payment Service
clears and settles this
payment internally.

6 days

SETTLED

The WorldPay
Payment Service
settles the payment to
you.

X days

SETTLED

The settlement to you

occurs according to
your settlement cycle.

34

About Testing the Integration

99Bill: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_99Bill_Order">
<description>test order</description>
<amount value="1000" currencyCode="CNY" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<NINETYNINEBILL-SSL shopperCountryCode="CN">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</NINETYNINEBILL-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Example: Redirect Model

The following example shows an XML order for the redirect integration model. This XML
order enables the shopper to make a payment by using either 99Bill or Alipay only.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="jsxml229005515">
<description>test order</description>
<amount value="1000" currencyCode="CNY" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentMethodMask>
<include code="NINETYNINEBILL-SSL"/>
<include code="ALIPAY-SSL"/>
</paymentMethodMask>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

35

Alternative Payment Methods Guide

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper. The shopper must also reenter the email address on the 99Bill website to obtain a
transaction receipt.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

Abaqoos
Abaqoos is an eWallet that shoppers can use when shopping on the Internet. To use this
service, the shopper must sign up for an Abaqoos eWallet.
To make a payment by using this method:
1. On the payment page, the shopper selects the Abaqoos payment method. The
shopper is redirected to the Abaqoos website.
2. The shopper logs on to the Abaqoos eWallet, and then makes the payment.
Additionally, within their wallet, the shopper must nominate the merchants to whom they
authorise transactions to be made. Transactions to non-authorised merchants fail at the point
when the PSP authorises the transaction.

36

About Testing the Integration

Payment Method Properties

The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet and Pre-pay voucher

Country

Hungary

Acceptance Currency and

Preferred Currency

HUF

Settlement to WorldPay
Currency

HUF

Minimum Amount for a Single

Transaction

No minimum

Maximum Amount for a Single

Transaction

500,000 HUF

Direct Refunds (Y/N)

No

Chargebacks (Y/N)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

ABAQOOS-SSL

statementNarrative (Yes/No)

No

37

Alternative Payment Methods Guide

Abaqoos: Example XML Order

Example: Direct Model
The following example shows an XML order that you can submit in the direct integration
model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Abaqoos_Order'>
<description>Description here</description>
<amount currencyCode='HUF' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<ABAQOOS-SSL shopperCountryCode='HU'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</ABAQOOS-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory details that require specific handling.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

The amount cannot include fractions of a HUF. If you pass

fractions of HUF:

Direct model: The following exception is returned:

<paymentService version="1.4"
merchantCode="XXXXX"><reply><error
code="5"><![CDATA[Fractional number of minor currency
units]]></error></reply></paymentService

Amount (value)

Redirect model: The Abaqoos payment method is not

offered on the WorldPay payment pages.

We therefore recommend that you:

Price your goods and services accordingly.

Ensure that you allow shoppers using this payment method

38

About Testing the Integration

to only request payment in HUF.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

AGMO
AGMO is a PSP based in the Czech Republic. AGMO offers a range of payment services,
including:
Premium SMS (sending SMS to a premium number).
ePayment (internet payment).
mPayment (mobile payment).
Premium Voice (calls to premium voice phone numbers) and credit cards.
The WorldPay Payment Service supports the AGMO ePayment+ service. The shopper does
not have to register with AGMO to use the service. AGMO only provides a gateway to the
shopper's online bank interface.
To use this payment method:
1. On the payment page, the shopper selects the AGMO payment method. The shopper
is redirected to the AGMO payment pages.
2. The shopper selects the online bank from which the payment must be made. The
shopper is redirected to the website of the bank.
3. The shopper logs on to the bank, and then makes the payment.

39

Alternative Payment Methods Guide

Payment Method Properties

The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Country

Czech Republic

Default Language

cs

Supported Language

cs

Acceptance Currency and

Preferred Currency

CZK

Settlement to WorldPay
Currency

CZK

Minimum Amount for a Single

Transaction

10 CZK

Maximum Amount for a Single

Transaction

50,000 CZK

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk

of chargeback to merchants.

statementNarrative (Yes/no)

No

Payment Method Mask

AGMO-SSL

statementNarrative (Yes/no)

No

40

About Testing the Integration

Payment Delays and Status Changes
After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Delay

Payment Status

Notes

Shopper
chooses the
payment
method.

SHOPPER_REDIR
ECTED

The payment is created in the

SHOPPER_REDIRECTED
status.

Shopper
makes the
payment.

X
minutes

SHOPPER_REDIR
ECTED

PSP
authorises
the
payment.

AUTHORISED

The
WorldPay
Payment
Service
captures
the
payment.

Less
than 1
hour

CAPTURED

The
WorldPay
Payment
Service
clears and
settles this
payment
internally.

5 days

SETTLED

The
WorldPay
Payment
Service
settles the
payment to
the
merchant.

X days

The settlement to you occurs

according to your settlement
cycle.

41

Alternative Payment Methods Guide

AGMO: Example XML Order

Example: Direct Model
The following example shows an XML order that you can submit in the direct integration
model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_AGMO_Order">
<description>test order</description>
<amount value="1000" currencyCode="NOK" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<AGMO-SSL shopperCountryCode="CZ">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</AGMO-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

42

About Testing the Integration

Alipay
Alipay is an eWallet that shoppers can use to make online payments securely. Alipay
partners with more than 65 financial institutions. To use this service, the shopper must sign
up for an Alipay account.
To make a payment by using this method:
1. On the payment page, the shopper selects the Alipay payment method. The shopper
is redirected to the Alipay payment pages.
2. The shopper logs on to the Alipay account, and then makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Country

China

Acceptance Currencies

AUD, CAD, CHF, DKK, EUR, GBP, HKD, NOK, SEK,

SGD, and USD

Settlement to WorldPay
Currency

Settlement is in the same currency as the acceptance

currency

Minimum Amount for a Single

Transaction

No minimum

Maximum Amount for a Single

Transaction

No maximum

Direct refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

ALIPAY-SSL

statementNarrative (Yes/No)

Yes

43

Alternative Payment Methods Guide

Alipay: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Alipay_Order">
<description>test order</description>
<amount value="1000" currencyCode="EUR" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<ALIPAY-SSL shopperCountryCode="CN">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</ALIPAY-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<statementNarrative>Example_Alipay_Narrative</statementNarrative>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the parameters that require specific handling.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper. The shopper must also re-enter
the email address on the 99Bill website, to obtain a transaction
receipt.

44

About Testing the Integration

BankAxess
BankAxess is a payment service in Norway. BankAxess is delivered through a collaboration
of Norwegian banks. The purpose of the service is enable merchants to take payments from
shoppers at any participating bank using a common set of credentials. The shopper must preregister for a BankID before using this service.
To make a payment by using this method:
1. On the payment page, the shopper selects the BankAxess payment method. The
BankAxess wizard appears.
2. The shopper logs on and makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Default Language

no (Norwegian)

Supported Language

no (Norwegian)

Country

Norway

Acceptance Currency

NOK

Settlement to WorldPay
Currency

NOK

Minimum Amount for a Single

Transaction

1 NOK

Maximum Amount for a Single

Transaction

50,000 NOK

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

BANKAXESS-SSL

statementNarrative (Yes/No)

No

45

Alternative Payment Methods Guide

Payment Delays and Status Changes
After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Delay

Payment Status

Notes

Shopper
chooses the
payment
method.

SHOPPER_REDIRE
CTED

The payment is created in the

SHOPPER_REDIRECTED
status.

Shopper
makes the
payment.

X
minutes

SHOPPER_REDIRE
CTED

PSP
authorises
the
payment.

AUTHORISED

The
WorldPay
Payment
Service
captures
the
payment.

Less
than 1
hour

CAPTURED

The
WorldPay
Payment
Service
clears and
settles this
payment
internally.

6 days

SETTLED

The
WorldPay
Payment
Service
settles the
payment to
the
merchant.

X days

The settlement to you occurs

according to your settlement
cycle.

46

About Testing the Integration

BankAxess: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_BankAxess_Order">
<description>test order</description>
<amount value="1000" currencyCode="NOK" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<BANKAXESS-SSL shopperCountryCode="NO">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</BANKAXESS-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the XML order parameters that require specific handling.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper. The shopper must also re-enter
the email address on the 99Bill website to obtain a transaction
receipt.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

47

Alternative Payment Methods Guide

Banklink NORDEA
Banklink is a real-time bank transfer payment service, which is available in Latvia. To use this
service, the shopper must have an account at one of the supporting banks.
To make a payment by using this method:
1. On the payment page, the shopper selects the Banklink payment method. The
shopper is redirected to the Banklink website.
2. The shopper logs into their Banklink account and makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Country

Latvia

Acceptance Currencies

LVL and EUR

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

No minimum

Maximum Amount for a Single

Transaction

10,000 LVL

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

BANKLINKNORDEA-SSL

statementNarrative (Yes/No)

No

48

About Testing the Integration

Banklink NORDEA: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_BanklinkNordea_order'>
<description>Description here</description>
<amount currencyCode='LVL' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<BANKLINKNORDEA-SSL shopperCountryCode='LV'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</BANKLINKNORDEA-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

49

Alternative Payment Methods Guide

BillingPartner
BillingPartner is a real-time bank transfer service available in Germany.
To make a payment by using this method:
1. On the payment page, the shopper selects the BillingPartner payment method. The
shopper is redirected to the BillingPartner website.
2. The shopper selects the required bank from which the payment must be made. The
shopper is redirected to the website of the bank.
3. The shopper logs on to the bank, and then makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Country

Germany

Authorisation and Preferred

Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

No minimum

Maximum Amount for a Single

Transaction

5,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

BILLINGPARTNER-SSL

statementNarrative

No

50

About Testing the Integration

BillingPartner: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_BillingPartner_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<BILLINGPARTNER-SSL shopperCountryCode='DE'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</BILLINGPARTNER-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

51

Alternative Payment Methods Guide

CashU
CashU is an eWallet that shoppers can use in a number of countries to make online
payments.
To make a payment by using this method:
1. On the payment page, the shopper selects the CashU payment method. The shopper
is redirected to the CashU website.
2. The shopper logs on to the CashU eWallet, and then confirms the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Countries

Bahrain, Canada, Egypt, Israel, Jordan, Kuwait,

Lebanon, Malaysia, Mauritania, Morocco, Oman,
Qatar, Russia, Saudi Arabia, Tanzania, Tunisia,
Turkey, Ukraine, United Arab Emirates, Uruguay, and
Venezuela

Acceptance Currency and

Preferred Currency

USD

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

3,200 USD

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

CASHU-SSL

statementNarrative (Yes/No)

No

52

About Testing the Integration

CashU: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<!DOCTYPE paymentService PUBLIC '-//Bibit//DTD Bibit PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_CashU_order'>
<description>Description here</description>
<amount currencyCode='USD' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<CASHU-SSL shopperCountryCode='BH'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</CASHU-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

53

Alternative Payment Methods Guide

Euteller
Euteller is a real-time bank transfer service that enables merchants to accept payments
directly from the shoppers online bank.
To make a payment by using this method:
1. On the payment page, the shopper selects the Euteller payment method. The
shopper is redirected to the Euteller website.
2. The shopper selects the bank from which the payment must be made. The shopper
is redirected to the website of the selected bank.
3. The shopper logs on to the bank, and then confirms the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Country

Finland

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 EUR

Maximum Amount for a Single

Transaction

10,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

EUTELLER-SSL

statementNarrative (Yes/No)

No

54

About Testing the Integration

Euteller: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_EUTeller_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<EUTELLER-SSL shopperCountryCode='FI'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</EUTELLER-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

55

Alternative Payment Methods Guide

eWire
eWire is an eWallet service that is available in Denmark, Norway, and Sweden.
To make a payment by using this method:
1. On the payment page, the shopper selects the eWire payment method. The shopper
is redirected to the eWire website.
2. The shopper selects the required bank from which the payment must be made. The
shopper is redirected to the website of the bank.
3. The shopper logs on to the bank, and then completes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Countries

Denmark, Norway, and Sweden

Acceptance Currency and

Preferred Currency

Settlement to WorldPay
Currency

Minimum Amount for a Single

Transaction

Maximum Amount for a Single

Transaction

Direct Refunds (Yes/No)

Denmark: DKK

Norway: NOK

Sweden: SEK

Denmark: DKK

Norway: NOK

Sweden:SEK

Denmark: 5 DKK

Norway: 5 NOK

Sweden:5 SEK

Denmark: 3,000 DKK

Norway: 1,000 NOK

Sweden:1,000 SEK

Yes

56

About Testing the Integration

Chargebacks (Yes/No)

Payment Method Mask

statementNarrative (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Denmark: EWIREDK-SSL

Norway: EWIRENO-SSL

Sweden: EWIRESE-SSL

No

eWire: Example XML Orders

Examples: Direct Model
This section includes example XML orders for the Denmark, Norway, and Sweden variants of
the eWire payment method.
Denmark
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_EWIREDK_order'>
<description>Description here</description>
<amount currencyCode='DKK' value='500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<EWIREDK-SSL shopperCountryCode='DK'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</EWIREDK-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

57

Alternative Payment Methods Guide

Norway
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_EWIRENO_order'>
<description>Description here</description>
<amount currencyCode='NOK' value='500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<EWIRENO-SSL shopperCountryCode='NO'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</EWIRENO-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Sweden
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_EWIRESE_order'>
<description>Description here</description>
<amount currencyCode='SEK' value='1800' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<EWIRESE-SSL shopperCountryCode='SE'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</EWIRESE-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

58

About Testing the Integration

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

InstaDebit
InstaDebit is a popular bank transfer payment method in Canada that shoppers can use to
transfer funds instantly and securely from their bank account to merchants, without revealing
any personal banking information. To use this payment method, shoppers must register for
an InstaDebit account and have a bank account with a supporting Canadian bank.
To make a payment by using this method:
1. On the payment page, the shopper selects the InstaDebit payment method. The
shopper is redirected to the InstaDebit website.
2. The shopper validates the payment transaction on the InstaDebit website.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Bank transfer

Country

Canada

Acceptance Currencies

CAD and USD

Settlement to WorldPay
Currency

Settlement is in the same currency as the acceptance

currency

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

50,000 USD

Direct Refunds (Yes/No)

Yes

59

Alternative Payment Methods Guide

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

INSTADEBIT-SSL

statementNarrative (Yes/No)

No

InstaDebit: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_InstaDebit_order'>
<description>Description here</description>
<amount currencyCode='CAD' value='500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<INSTADEBIT-SSL shopperCountryCode='CA'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</INSTADEBIT-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Joe</firstName>
<lastName>Bloggs</lastName>
<address1>1 Riverside Street</address1>
<postalCode>T1Y 2C3</postalCode>
<city>Calgary</city>
<countryCode>CA</countryCode>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

60

About Testing the Integration

Mandatory Data
The following table lists the mandatory data that require specific handling.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

firstName

If you do not include these values in your order:

lastName

Direct model: The WorldPay Payment Service returns an

error.

Redirect model: The shopper is prompted to type this value

on the WorldPay payment pages.

The firstName and lastName parameters are sub-elements of a parent. In the direct model,
the additional parameters listed in the following table are therefore mandatory.

In the redirect model, you must include these values if the shippingAddress
element is present.

Parameter Name

Description

Address1

The first line of the shopper's shipping address.

postalCode

The postal code of the shopper's shipping address.

city

The city of the shopper's shipping address.

countryCode

The country code of the shopper's shipping address.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

61

Alternative Payment Methods Guide

Mister Cash
Mister Cash/Bancontact is a debit card service available in Belgium. Shoppers can use this
service to make real-time card payments for products and services. To use this service,
shoppers must sign up for a Mister Cash debit card. The use of Mister Cash-branded cards is
very high in Belgium and it is a widely-accepted method of payment.
To make a payment by using this method:
1. On the payment page, the shopper selects the Mister Cash card payment method.
The shopper is redirected to the Mister Cash website.
2. The shopper authorises the payment on the Mister Cash website.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Debit card payment

Country

Belgium

Acceptance Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

No minimum

Maximum Amount for a Single

Transaction

5,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Direct Refunds (Yes/No)

No

Payment Method Mask

MISTERCASH-SSL

statementNarrative (Yes/No)

No

62

About Testing the Integration

MisterCash: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Mister_Cash_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<MISTERCASH-SSL shopperCountryCode='BE'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</MISTERCASH-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Pierre</firstName>
<lastName>Bloggs</lastName>
<address1>Shopperstreet</address1>
<postalCode>1234</postalCode>
<city>Shoppercity</city>
<countryCode>BE</countryCode>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

firstName*

The first name of the shopper.

lastName*

The last name of the shopper.

address1*

The first line of the shopper's shipping

address, commonly the street name.

postalCode*

The shipping postal code/zip code.

63

Alternative Payment Methods Guide

city*

The city of the shopper's shipping address.

countryCode*

The country of the shopper's shipping

address.

* This value is displayed to the shopper on the PSP payment pages.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

NeoSurf
Neosurf Classic is a pre-pay voucher payment method. The shopper purchases a voucher
from an outlet such as a newsagent. The voucher has a face value and the shopper can
make purchases up to the voucher value. Any unused value is retained on the voucher for
future use.
Neosurf state that their service facilitates the purchase of low value items such as mobile
services such as ringtones and mobile games, online games, music, photographs, and gifts.
To make a payment by using this method:
1. On the payment page, the shopper selects the Neosurf payment method. The
shopper is redirected to the Neosurf website.
2. The shopper enters the voucher number. Neosurf validates the voucher and returns
a real-time notification of payment to WorldPay.

64

About Testing the Integration

Payment Method Properties

The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay voucher

Countries

Belgium, France, Italy, and Spain

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

No minimum

50,000 EUR
Maximum Amount for a Single
Transaction

Note: In practice, the maximum amount is EUR 100,

which is the maximum value of a single
voucher. Because shoppers can consolidate multiple
vouchers, the maximum amount can be slightly more
than EUR 100.

Direct Refunds (Yes/No)

No.

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

NEOSURF-SSL

statementNarrative (Yes/No)

No

65

Alternative Payment Methods Guide

Neosurf: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Neosurf_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='7500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<NEOSURF-SSL shopperCountryCode='FR'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</NEOSURF-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

66

About Testing the Integration

Paga Verve
Verve is a debit card brand in Nigeria. Paga offers a service, whereby it accepts Verve
payments on behalf of merchants, enabling Verve cardholders to pay for purchases online.
To make a payment by using this method:
1. On the payment page, the shopper selects the Paga Verve payment method. The
shopper is redirected to the Paga website.
2. The shopper completes the payment by providing the debit card details.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Debit card

Country

Nigeria

Default Language

en

Supported Language

en

Acceptance Currency and

Preferred Currency

USD

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

620 USD

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

PAGA_VERVE-SSL

statementNarrative (Yes/No)

No

67

Alternative Payment Methods Guide

Paga Verve: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Paga_Verve_order'>
<description>Description here</description>
<amount currencyCode='USD' value='500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<PAGA_VERVE-SSL shopperCountryCode='NG'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</PAGA_VERVE-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

68

About Testing the Integration

Paga Wallet
Paga Wallet is an eWallet service that shoppers can use to make payments online. The
eWallet can be topped up with cash at any outlet in the Paga agent network. This payment
method is therefore suitable for accepting payments from shoppers who do not have a bank
account or payment card.
To make a payment by using this method:
1. On the payment page, the shopper selects the Paga Wallet payment method. The
shopper is redirected to the Paga website.
2. The shopper logs on to the Paga website and confirms the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Country

Nigeria

Default Language

en

Supported Language

en

Acceptance Currency and

Preferred Currency

USD

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

620 USD

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

PAGA-SSL

statementNarrative

No

69

Alternative Payment Methods Guide

Paga Wallet: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Paga_Verve_order'>
<description>Description here</description>
<amount currencyCode='USD' value='500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<PAGA-SSL shopperCountryCode='NG'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</PAGA-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

70

About Testing the Integration

Paysafecard
Paysafecard is a prepaid card that shoppers can use to make online payments. A shopper
can purchase Paysafecard prepaid cards at a local shop by using cash or another payment
method.
The Paysafecard service states that it is aimed at the following groups of shoppers:
Shoppers who do not want to use their payment cards online.
Shoppers who do not have a payment card.
Shoppers from younger age groups.
Shoppers who prefer cash payments.
Paysafecard also states that this payment method is suited businesses involving online
entertainment such as games, social media, telephony and messaging, Internet services, and
betting.
To make a payment by using this method:
1. On the payment page, the shopper selects the Paysafecard payment method. The
shopper is redirected to the Paysafecard website.
2. The shopper validates the payment transaction by entering a unique 16-digit PIN
number.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay card

Countries

Austria, Belgium, Cyprus, Czech Republic, Denmark,

France, Germany, Greece, Ireland, Italy,
Liechtenstein, Luxembourg, Netherlands, Norway,
Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland, and United Kingdom

Acceptance Currencies

CHF, CZK, DKK, EUR, RON, GBP, NOK, PLN, SEK,

and USD

Preferred Currency

CHF

Settlement to WorldPay
Currency

Payments made in RON are settled in EUR.

Payments made with any other acceptance currency
are settled in the same currency.

Minimum Amount for a Single

Transaction

No minimum

71

Alternative Payment Methods Guide

Maximum Amount for a Single

Transaction

10,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk

of chargeback to merchants.

Payment Method Mask

PAYSAFECARD-SSL

statementNarrative (Yes/No)

No

Paysafecard: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Paysafecard_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='1000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<PAYSAFECARD-SSL shopperCountryCode='NL'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</PAYSAFECARD-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

72

About Testing the Integration

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

POLi
POLi is real-time bank transfer payment method that shoppers can use to make real-time
payments directly from their online bank account.
To make a payment by using this method:
1. On the payment page, the shopper selects the POLi payment method. The shopper
is redirected to the POLi website.
2. The shopper selects the bank from which the payment must be made. The shopper
is redirected to the website of the bank.
3. The shopper logs on to the bank and makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Countries

Australia and New Zealand

Default Language

en

Supported Languages

en

Acceptance Currency and

Preferred Currency

Settlement to WorldPay
Currency

Minimum Amount for a Single

Transaction

Australia: AUD
New Zealand: NZD
Australia: AUD
New Zealand: NZD

Australia: No minimum

73

Alternative Payment Methods Guide

New Zealand: 1 NZD

Australia: 501 AUD

Maximum Amount for a Single

Transaction

New Zealand: 501 NZD

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.
Australia: POLI-SSL

Payment Method Mask

New Zealand: POLINZ-SSL
statementNarrative

No

POLi: Example XML Orders

Example: Direct Model
This section includes example XML orders for the Australia and New Zealand variants of the
POLi payment method.
Australia
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Poli_order'>
<description>Description here</description>
<amount currencyCode='AUD' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<POLI-SSL shopperCountryCode='AU'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</POLI-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

74

About Testing the Integration

New Zealand
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_PoliNZ_order'>
<description>Description here</description>
<amount currencyCode='NZD' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<POLINZ-SSL shopperCountryCode='NZ'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</POLINZ-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

75

Alternative Payment Methods Guide

Postepay
Postepay is a prepaid card service that is branded with Visa Electron and operated by Poste
Italiane in Italy. Postepay cards are accepted wherever Visa Electron is supported. When a
shopper makes a payment, funds are immediately deducted from the card.
A shopper does not require a bank account to obtain a Postepay card. The shopper must
purchase the card at a post office and provide the required identity documents. The shopper
must also register it online.
To make a payment by using this card:
1. On the payment page, the shopper selects the Postepay payment method. The
shopper is redirected to the Postepay website.
2. The shopper completes the payment by providing the card details.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay card

Country

Italy

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 EUR

Maximum Amount for a Single

Transaction

1,000 EUR

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk

of chargeback to merchants.

Payment Method Mask

POSTEPAY-SSL

statementNarrative (Yes/No)

No

76

About Testing the Integration

PostePay: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Postepay_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<POSTEPAY-SSL shopperCountryCode='IT'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</POSTEPAY-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

77

Alternative Payment Methods Guide

SOFORT Banking
Sofort Banking (SOFORT berweisung) is a real-time bank transfer payment method that
shoppers based in Austria, France, and Germany can use to transfer funds directly to
merchants from their bank accounts.
To make a payment by using this method:
1. On the payment page, the shopper selects the SOFORT Banking payment method.
The shopper is redirected to the SOFORT Banking website.
2. The shopper reviews the order details and selects the required bank from which the
payment must be made. The shopper is redirected to the website of the bank.
3. The shopper logs on to the bank, and then confirms the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Countries

Austria, France, and Germany

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

No minimum

Maximum Amount for a Single

Transaction

2,000 EUR

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

SOFORT-SSL

statementNarrative

No

78

About Testing the Integration

SOFORT Banking: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Sofort_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<SOFORT-SSL shopperCountryCode='DE'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</SOFORT-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

79

Alternative Payment Methods Guide

Sporopay
Sporopay is a real-time banking payment service offered by the Slovensk Sporitea bank in
Slovakia. Shoppers can use this service to make payments directly to merchants from their
online bank accounts.
To make a payment by using this method:
1. On the payment page, the shopper selects the Sporopay payment method. The
shopper is redirected to the Slovensk Sporitea website.
2. The shopper confirms the payment on the Slovensk Sporitea website.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Country

Slovakia

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 EUR

Maximum Amount for a Single

Transaction

500 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

SPOROPAY-SSL

statementNarrative (Yes/No)

No

80

About Testing the Integration

Sporopay: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Sporopay_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<SPOROPAY-SSL shopperCountryCode='SK'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</SPOROPAY-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

81

Alternative Payment Methods Guide

Ticket Premium
Ticket Premium is a prepaid card that shoppers can use to make online payments. A shopper
can buy a Ticket Premium card offline, for example from a newsagent, and then use it to
make payments online.

Ticket Premium and Ticket Surf are two different APMs offered by Ticket Surf
International (TSI).
1. Ticket Premium is used by shoppers over 18s. Shoppers can use this APM
to make payments for a wide variety of goods and services, including
gambling. This APM is supported by the WorldPay Payment Service.
2. Ticket Surf is used by shoppers from younger age groups. This APM is
currently not supported by the WorldPay Payment Service.

To make a payment by using this method:

1. On the payment page, the shopper selects the Ticket Premium payment method. The
shopper is redirected to the Ticket Premium website.
2. The shopper completes the payment on the Ticket Premium website.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay card

Country

France

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 EUR

Maximum Amount for a Single

Transaction

5,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk

of chargeback to merchants.

82

About Testing the Integration

Payment Method Mask

TICKETSURF-SSL

statementNarrative (Yes/No)

No

Ticket Premium: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Ticket_Premium_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<TICKETSURF-SSL shopperCountryCode='FR'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</TICKETSURF-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

83

Alternative Payment Methods Guide

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

TrustPay
TrustPay is a real-time bank transfer payment service, which is widely used in the Czech
Republic, Estonia and Slovakia.
To make a payment by using this method:
1. On the payment page, the shopper selects the TrustPay payment method. The
shopper is redirected to the TrustPay website.
2. The shopper selects the bank from which the payment must be made. The shopper
is redirected to the website of the online bank.
3. The shopper logs on to the bank and makes the payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Countries

Czech Republic, Estonia, and Slovakia

Czech Republic: EUR and CZK

Acceptance Currency and

Preferred Currency

Estonia: EUR
Slovakia: EUR
Czech Republic: EUR and CZK

Settlement to WorldPay
Currency

Estonia: EUR
Slovakia: EUR

Minimum Amount for a Single

Transaction

No minimum

84

About Testing the Integration

Czech Republic: 5,000 CZK

Maximum Amount for a Single
Transaction

Estonia: 5,000 EUR

Slovakia: 5,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.
Czech Republic: TRUSTPAY_CZ-SSL
Estonia: TRUSTPAY_EE-SSL

Payment Method Mask

Slovakia: TRUSTPAY_SK-SSL
statementNarrative (Yes/No)

No

TrustPay: Example XML Order

Example: Direct Model
This section includes example XML orders for the Czech Republic, Estonia, and Slovakia
variants of the TrustPay payment method.
Czech Republic
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_TrustPay_CZ_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='1000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<TRUSTPAY_CZ-SSL shopperCountryCode='CZ'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</TRUSTPAY_CZ-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

85

Alternative Payment Methods Guide

Estonia
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_TrustPay_EE_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='1000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<TRUSTPAY_EE-SSL shopperCountryCode='EE'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</TRUSTPAY_EE-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Slovakia
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_TrustPay_SK_order'>
<description>Description here</description>
<amount currencyCode='EUR' value='1000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<TRUSTPAY_SK-SSL shopperCountryCode='SK'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</TRUSTPAY_SK-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

86

About Testing the Integration

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

WebMoney
WebMoney is an eWallet that shoppers can use to make real-time online payments. The
shoppers WebMoney account, also known as a purse, can be denominated in Russian
Roubles, US dollars, Euros, and other currencies. Although it was originally launched in
Russia, WebMoney is now used globally.
To make a payment by using this method:
1. On the payment page, the shopper selects the WebMoney payment method. The
shopper is redirected to the WebMoney website.
2. The shopper confirms the payment on the WebMoney website.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Countries

Armenia, Azerbaijan, Belarus, China, Georgia,

Kazakhstan, Kyrgyzstan, Latvia, Lithuania, Moldova,
Russia, Tajikistan, Turkmenistan, Ukraine, and
Uzbekistan

Acceptance Currencies

RUB, USD, and EUR

Preferred Currency

USD

Settlement to WorldPay
Currency

Payments made in RUB and USD are settled in USD.

Payments made in EUR are settled in EUR only.

Minimum Amount for a Single

Transaction

10 USD

Maximum Amount for a Single

2,000 USD

87

Alternative Payment Methods Guide

Transaction
Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

WEBMONEY-SSL

statementNarrative

No

WebMoney: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_WebMoney_order'>
<description>Description here</description>
<amount currencyCode='RUB' value='40000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<WEBMONEY-SSL shopperCountryCode='RU'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</WEBMONEY-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

88

About Testing the Integration

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

Yandex.Money
Yandex.Money is an eWallet that shoppers can use to make real-time online payments.
Although it was originally launched in Russia, Yandex.Money is now used globally.
To make a payment by using this method:
1. On the payment page, the shopper selects the Yandex.Money payment method. The
shopper is redirected to the Yandex.Money website.
2. They shopper logs on to their Yandex.Money eWallet, and then confirms the
payment.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Countries

Armenia, Azerbaijan, Belarus, Georgia, Kazakhstan,

Kyrgyzstan, Moldova, Russia, Tajikistan,
Turkmenistan, Ukraine, and Uzbekistan

Acceptance Currencies

RUB and USD

Preferred Currency

USD

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

640 USD

89

Alternative Payment Methods Guide

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

YANDEXMONEY-SSL

statementNarrative

No

Yandex.Money: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_YandexMoney_order'>
<description>Description here</description>
<amount currencyCode='RUB' value='40000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<YANDEXMONEY-SSL shopperCountryCode='RU'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</YANDEXMONEY-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

90

About Testing the Integration

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

Delayed Hybrid APMs

When a shopper makes a payment by using a delayed hybrid payment method, the PSP
completes the payment without prompting the shopper for any further information. The
payment pages of the PSP are therefore invisible to the shopper.
Delayed hybrid payments are not authorised immediately. Funds are transferred into your
account depending on the payment processing policies of the PSP.

Baloto
Baloto is a popular cash payment method in Colombia. Shoppers can purchase online and
then make payments at a supporting Baloto payment outlet.
To make a payment by using this method:
1. On the payment page, the shopper selects the Baloto payment method. The shopper
is redirected to a secure Baloto page.
2. The shopper reviews the summary of the transaction. Then shopper is redirected to
the PagosOnline Baloto page and presented with two payment codes.
3. The shopper makes the payment at a Baloto payment outlet by using the payment
codes.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description

Payment Type

Post-pay voucher

Country

Colombia

Acceptance Currency

COP

Settlement to WorldPay
Currency

USD

91

Alternative Payment Methods Guide

Minimum Amount for a Single

Transaction

5,000 COP

Maximum Amount for a Single

Transaction

500,000 COP

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

BALOTO-SSL

statementNarrative (Yes/No)

No

Boleto Bancrio
Boleto Bancrio is a post-payment service that allows a shopper to pay for online services
either using a bank account or over the counter at any supporting outlet in Brazil. Boleto
Bancrio is a popular solution for invoice payments in Brazil.
A shopper does not require an account with Boleto Bancrio to make payments using this
method. However, the shopper must have a Cadastro de Pessoas Fsicas (CPF), which is a
fiscal number.
To make a payment by using this payment method:
1. On the payment page, the shopper selects the Boleto Bancrio payment method.
1. The shopper types and confirms additional data such as the name and address. The
shopper is redirected to the Boleto Bancrio website, where a payment voucher is
displayed.
2. The shopper prints the voucher and makes the payment by either logging on to their
Internet bank, or paying over the counter.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description

Payment Type

Post-pay voucher

Country

Brazil

Default Language

en

Supported Languages

pt and en

92

About Testing the Integration

Acceptance Currency and

Preferred Currency

BRL

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

18 BRL

Maximum Amount for a Single

Transaction

6,400 BRL

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

BOLETO-SSL

statementNarrative (Yes/No)

No

Payment Delays and Status Changes

After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action
Shopper
chooses the
payment
method.

Shopper makes
the payment.

Delay

X
days

Payment Status

Notes

SHOPPER_REDIRECTED

The payment is created

in the
SHOPPER_REDIRECT
ED status.

SHOPPER_REDIRECTED

The shopper must make

the payment within five
days. However, a
voucher presented after
this deadline might still
be accepted.

93

Alternative Payment Methods Guide

Bank/PSP
authorises the
payment.

AUTHORISED

The payment is
authorised the same
working day.

The WorldPay
Payment
Service
captures the
payment.

Less
than
1
hour

CAPTURED

The WorldPay
Payment
Service clears
and settles this
payment
internally.

5
days

SETTLED

The WorldPay
Payment
Service settles
the payment to
you.

X
days

SETTLED

The settlement to you

occurs according to your
settlement cycle.

Boleto Bancrio: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Boleto_Order">
<description>test order</description>
<amount value="2000" currencyCode="BRL" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<BOLETO-SSL shopperCountryCode="BR">
<cpf>39053344705</cpf>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</BOLETO-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Joe</firstName>
<lastName>Bloggs</lastName>

94

About Testing the Integration

<address1>Rua Castilho 34</address1>
<address2>Santo Andr</address2>
<address3> </address3>
<postalCode>04642-000</postalCode>
<city>So Paulo</city>
<state>So Paulo</state>
<countryCode>BR</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order and
parameters that require special handling.

Parameter Name

Description

CPF or CNPJ

The CPF (Cadastro de Pessoas Fsicas) is a unique number

assigned by the Brazilian tax authorities to economically active
individuals in Brazil. This number is primarily used to estimate
the income tax due. Some payment providers might also use
this number to assist in detecting money laundering and other
criminal activities.
The CNPJ is similar to CPF, but applies to businesses rather
than individuals.
The CPF or CPNJ field is 11- 15 characters long, and must
appear in the paymentDetails block.

shopperEmailAddress

The email address of the shopper.

firstName

The first name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

lastName

The last name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

address1

The first line of the shopper's address.

city

The shopper's city.

state

The shopper's state.

postalCode

The shopper's postal code.

The firstName, lastName and telephoneNumber are elements that are mandated by the
PSP for this payment method. Because these elements are sub-elements of a parent
element in the XML schema, you must also pass other mandatory sub-elements such as the
countryCode.
95

Alternative Payment Methods Guide

Optional Data
The following table lists the optional parameters that require special handling.

Parameter
Name

Description

address2

The second line of the shopper's address.

address3

The third line of the shopper's address.

DineroMail 7eleven and DineroMail Oxxo

DineroMail is a PSP that offers a range of payment methods in South America and beyond.
Shoppers can order goods and services online, and pay by using use these payment
methods at one of the 7eleven or OXXO convenience stores available throughout Mexico. A
shopper does not require an account with DineroMail to make payments using this method.
To make a payment by using this method:
1. On the payment page, the shopper selects the DineroMail OXXO or DineroMail
7eleven payment method.
2. The shopper types their name, email address, and phone number. After the shopper
confirms these details, the shopper is redirected to the DineroMail website, where
they print out a voucher containing a barcode.
3. The shopper presents the voucher and makes the payment at an OXXO or 7eleven
outlet.
During the payment journey, the shopper can optionally log on to their DineroMail account.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Post-pay voucher

Country

Mexico

Default Language

en

Supported Languages

es and en

Acceptance Currency and

Preferred Currency

MXN

96

About Testing the Integration

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

20 MXN

Maximum Amount for a Single

Transaction

20,000 MXN

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.
Dineromail
7eleven:DINEROMAIL_7ELEVEN-SSL

Payment Method Mask

Dineromail OXXO:DINEROMAIL_OXXOSSL
No

statementNarrative (Yes/No)

Payment Delays and Status Changes

After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Delay

Shopper
chooses the
payment
method.

Shopper makes
the payment.

X
hours
or
longe
r

Payment Status

Notes

SHOPPER_REDIRECTED

The payment is created

in the
SHOPPER_REDIRECT
ED status.

SHOPPER_REDIRECTED

The voucher expires

after 16 calendar days.
The shopper can make
the payment at any time
before the voucher
expires.

97

Alternative Payment Methods Guide

Bank/PSP
authorises the
payment.

1 day

AUTHORISED

The payment is
authorised the next
working day.

The WorldPay
Payment
Service
captures the
payment.

Less
than
1
hour

CAPTURED

The WorldPay
Payment
Service clears
and settles this
payment
internally.

7
days

SETTLED

The WorldPay
Payment
Service settles
the payment to
you.

X
days

SETTLED

The settlement to you

occurs according to your
settlement cycle.

DineroMail 7eleven and DineroMail Oxxo: Example XML Orders

Example: Direct Model
This section includes example XML orders for the DineroMail 7eleven and DineroMail Oxxo
payment methods.
DineroMail 7eleven
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Dineromail_7eleven_Order">
<description>test order</description>
<amount value="2000" currencyCode="MXN" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<DINEROMAIL_7ELEVEN-SSL shopperCountryCode="MX">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</DINEROMAIL_7ELEVEN-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>

98

About Testing the Integration

<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Ro Lerma 7199</address1>
<postalCode>06500</postalCode>
<city>Col Cuauhtmoc</city>
<countryCode>MX</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

DineroMail OXXO
The following example shows an XML order for the redirect integration model. This XML
order enables the shopper to make a payment by using either 99Bill or Alipay only.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Dineromail_OXXO_Order">
<description>test order</description>
<amount value="2000" currencyCode="MXN" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<DINEROMAIL_OXXO-SSL shopperCountryCode="MX">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</DINEROMAIL_OXXO-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Ro Lerma 7199</address1>
<postalCode>06500</postalCode>
<city>Col Cuauhtmoc</city>
<countryCode>MX</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

99

Alternative Payment Methods Guide

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

firstName

The first name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

lastName

The last name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

telephoneNumber

The telephone number of the shopper in the local or

international format. This parameter can contain numbers only. If
you include more than 20 characters, the telephone number is
truncated to 20 characters.
Note: If you include spaces or special characters in a Direct XML
order, the phone number is nullified. The shopper must then reenter it on the PSP pages.

The firstName, lastName and telephoneNumber are elements that are mandated by the
PSP for this payment method. Because these elements are sub-elements of a parent
element in the XML schema, you must also pass other mandatory sub-elements such as city.

Ensure that the firstName, lastName and telephoneNumber parameters contain

the actual shopper data. If the data for other mandatory parameters such as city and
address1 is unavailable, you can pass dummy values.

Response URL
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns the pendingURL.
However, in some cases, the shopper might close the browser after completing the payment,
but before reaching the pending URL. In such cases, the payment may ultimately be
authorised.

100

About Testing the Integration

DineroMail Bank Transfer

DineroMail is a PSP that offers a range of payment methods in South America and beyond.
The DineroMail Bank Transfer method enables merchants to receive payments directly from
the bank accounts of shoppers based in Mexico. A shopper does not require an account with
DineroMail to make payments by using this method.
The following banks are currently supported:
BBVA Bancomer
HSBC
IXE
Santander
Scotia Bank
To make a payment by using this method:
1. On the payment page, the shopper selects the DineroMail Bank Transfer payment
method.
2. The shopper types and confirms their name, email address, and phone number. The
shopper is redirected to the Dineromail website.
3. The shopper selects the bank from which the payment must be made, and agrees to
the terms and conditions. The shopper receives instructions about how to make the
payment through their Internet bank.
4. The shopper completes the payment by logging on to their Internet bank.
During the payment journey, the shopper can optionally log on to their DineroMail account.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Offline bank transfer

Country

Mexico

Default Language

en

Supported Languages

en and es

Acceptance Currency and

Preferred Currency

MXN

Settlement to WorldPay
Currency

USD

101

Alternative Payment Methods Guide

Minimum Amount for a Single

Transaction

20 MXN

Maximum Amount for a Single

Transaction

31,000 MXN

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

DINEROMAIL_ONLINE_BT-SSL

statementNarrative (Yes/No)

No

Payment Delays and Status Changes

After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Delay

Payment Status

Notes

SHOPPER_REDIRECTED

The payment is created

in the
SHOPPER_REDIRECT
ED status.

Shopper
chooses the
payment
method.

Shopper makes
the payment.

X
hours
or
longe
r

The shopper can make

the payment
immediately, but is not
obliged to do so.

Bank/PSP
authorises the
payment.

1 day

AUTHORISED

The payment is
authorised the next
working day.

The WorldPay
Payment
Service
captures the
payment.

Less
than
1
hour

CAPTURED

102

About Testing the Integration

The WorldPay
Payment
Service clears
and settles this
payment
internally.

7
days

SETTLED

The WorldPay
Payment
Service settles
the payment to
you.

X
days

The settlement to you

occurs according to your
settlement cycle.

DineroMail Offline Bank Transfer: Example XML Orders

Example: Direct Model
The following example shows an XML order that you can submit in the direct integration
model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Dineromail_BT_Order">
<description>test order</description>
<amount value="2000" currencyCode="MXN" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<DINEROMAIL_ONLINE_BT-SSL shopperCountryCode="MX">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</DINEROMAIL_ONLINE_BT-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Ro Lerma 7199</address1>
<postalCode>06500</postalCode>
<city>Col Cuauhtmoc</city>
<countryCode>MX</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

103

Alternative Payment Methods Guide

Mandatory Data
The following table lists the mandatory data that require specific handling.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

firstName

The first name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

lastName

The last name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.
The telephone number of the shopper in the local or international
format. This parameter can contain numbers only.

telephoneNumber

If you include more than 20 characters, the telephone number is

truncated to 20 characters
If you include spaces or special characters in a direct XML order,
the phone number is nullified. The shopper must then re-enter it on
the PSP pages.

The firstName, lastName and telephoneNumber are elements that are mandated by the
PSP for this payment method. Because these elements are sub-elements of a parent
element in the XML schema, you must also pass other mandatory sub-elements such as city.

Ensure that the firstName, lastName and telephoneNumber parameters contain

the actual shopper data. If the data for other mandatory parameters such as city and
address1 is unavailable, you can pass dummy values.

Example: Redirect Model

When you submit an XML order in the redirect model, we recommend that you provide the
data listed in the following table, if you have captured this data on your website.

Field

Source

First name

firstName

Last name

lastName

Email address

shopperEmailAddress

Telephone number

telephoneNumber

104

About Testing the Integration

If you capture this information on your website and pass it in your XML order, the appropriate
values are pre-populated on the WorldPay pages. The shopper does not need to provide the
same information twice, which optimises shopper experience.
Example with All Parameters
The following example shows an XML order, where the merchant has supplied all the
required parameters. The merchant has also included the payment method mask, which
ensures that the shopper can only choose from a range of payment methods.
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE paymentService PUBLIC "-//RBS
WorldPay//DTD RBS WorldPay PaymentService v1//EN"
"http://dtd.wp3.rbsworldpay.com/paymentService_v1.dtd"><paymentService
version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_DM_Redirect_Order">
<description>jsredirect test order</description>
<amount value="2000" currencyCode="MXN" exponent="2"/>
<orderContent>
<![CDATA[
]]>
</orderContent>
<paymentMethodMask>
<include code="DINEROMAIL_ONLINE_BT-SSL"/>
<include code="DINEROMAIL_OXXO-SSL"/>
<include code="DINEROMAIL_7ELEVEN-SSL"/>
</paymentMethodMask>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Ro Lerma 7199</address1>
<address2></address2>
<address3></address3>
<postalCode>06500</postalCode>
<city>Col Cuauhtmoc</city>
<state>Mxico DF</state>
<countryCode>MX</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

In the above example, the inclusion of the specified payment method masks ensures that the
shopper can only choose from the following three payment methods on the WorldPay
payment pages:
Dineromail Offline Bank Transfer.
Dineromail OXXO.
Dineromail 7Eleven.
Because the firstName, lastName and telephoneNumber are provided, the shopper is not
prompted to enter any data on the WorldPay pages. The shopper only has to select the
payment method they want to use.

105

Alternative Payment Methods Guide

Example with Some Required Parameters
The following example shows an XML order where the merchant has supplied some of the
parameters required for this payment method. In the payment method mask, the merchant
has specified that the shopper can choose from any available payment method.
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE paymentService PUBLIC "-//RBS
WorldPay//DTD RBS WorldPay PaymentService v1//EN"
"http://dtd.wp3.rbsworldpay.com/paymentService_v1.dtd"><paymentService
version="1.4" merchantCode="DEMO">
<submit>
<order orderCode="ORD433434">
<description>jsredirect test order</description>
<amount value="2000" currencyCode="MXN" exponent="2"/>
<orderContent>
<![CDATA[
]]>
</orderContent>
<paymentMethodMask>
<include code="ALL"/>
</paymentMethodMask>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Ro Lerma 7199</address1>
<address2></address2>
<address3></address3>
<postalCode>06500</postalCode>
<city>Col Cuauhtmoc</city>
<state>Mxico DF</state>
<countryCode>MX</countryCode>
<telephoneNumber></telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

In the above example, the shopper can choose any available payment methods on the
WorldPay payment pages. The merchant has included data for the firstName and lastName;
the shopper is therefore not prompted to enter these on the WorldPay pages. However,
because the telephoneNumber is not included, the shopper must type this value on the
extra data page on the WorldPay payment pages.
Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns the pendingURL.
However, in some cases, the shopper might close the browser after completing the payment,
but before reaching the pending URL. In such cases, the payment may ultimately be
authorised.

106

About Testing the Integration

DineroMail ServiPag
DineroMail is a PSP that offers a range of payment methods in South America and beyond.
Shoppers can use this payment method to order goods and services online, and pay at one
of the ServiPag outlets available throughout Chile. A shopper does not need an account with
DineroMail to make payments using this method.
To make a payment by using this method:
1. On the payment page, the shopper selects the DineroMail ServiPag payment
method.
2. The shopper types and confirms their name, email address and phone number. The
shopper is redirected to the DineroMail website.
3. The shopper prints out a voucher containing a barcode.
4. The shopper presents and pays the voucher at a ServiPag outlet.
During the payment journey, the shopper can optionally log on to their DineroMail account.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Post-pay voucher

Country

Chile

Default Language

en

Supported Languages

en and es

Acceptance Currency and

Preferred Currency

CLP

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1,200 CLP

Maximum Amount for a Single

Transaction

750,000 CLP

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.

107

Alternative Payment Methods Guide

There is a risk of chargeback to merchants.
Payment Method Mask

DINEROMAIL_SERVIPAG-SSL

statementNarrative (Yes/No)

No

Payment Delays and Status Changes

After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Delay

Payment Status

Notes

Shopper
chooses the
payment
method.

SHOPPER_
REDIRECTED

The payment is created in

the
SHOPPER_REDIRECTED
status.

Shopper makes
the payment.

X hours
or
longer

Bank/PSP
authorises the
payment.

1 day

AUTHORISED

The payment is authorised

the next working day.

The WorldPay
Payment
Service
captures the
payment.

Less
than 1
hour

CAPTURED

The WorldPay
Payment
Service clears
and settles this
payment
internally.

8 days

SETTLED

The WorldPay
Payment
Service settles
the payment to
you.

X days

The settlement to you

occurs according to your
settlement cycle.

108

About Testing the Integration

DineroMail ServiPag: Example XML Orders

Example: Direct Model
The following example shows an XML order that you can submit in the direct integration
model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Dineromail_Servipag_Order">
<description>test order</description>
<amount value="120000" currencyCode="CLP" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<DINEROMAIL_SERVIPAG-SSL shopperCountryCode="CL">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</DINEROMAIL_SERVIPAG-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Avda. El Bosque Norte 99996</address1>
<postalCode>832000</postalCode>
<city>Santiago</city>
<countryCode>CL</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the XML order parameters that require specific handling for the
DineroMail Offline Bank Transfer payment method.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

firstName

The first name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

lastName

The last name of the shopper. If you include more than 30

characters, the name is truncated to 30 characters.

109

Alternative Payment Methods Guide

The telephone number of the shopper in the local or international

format. If you include more than 20 characters, the telephone
number is truncated to 20 characters.
telephoneNumber
If you include spaces or special characters in a Direct XML order,
the phone number is nullified. The shopper must then re-enter it on
the PSP pages.

The firstName, lastName and telephoneNumber are elements that are mandated by the
PSP for this payment method. Because these elements are sub-elements of a parent
element in the XML schema, you must also pass other mandatory sub-elements such as city.

Ensure that the firstName, lastName and telephoneNumber parameters contain

the actual shopper data. If the data for other mandatory parameters such as city and
address1 is unavailable, you can pass dummy values.

Examples: Redirect Model

When you submit an XML order in the redirect model, we recommend that you provide the
data listed in the following table, if you have captured this data on your website.

Field

Source

First name

firstName

Last name

lastName

Email address

shopperEmailAddress

Telephone
number

telephoneNumber

The additional data page is pre-populated with the values that you pass in the XML order. If
you do not include these parameters in your order, the shopper is prompted to provide this
information on the WorldPay payment pages.
If you capture this information on your website and pass it in your XML order, the appropriate
values are pre-populated on the WorldPay pages. The shopper does not need to provide the
same information twice, which optimises shopper experience.

110

About Testing the Integration

Example with All Required Parameters
The following example shows an XML order, where the merchant has supplied all the
required parameters. The merchant has also included the payment method mask, which
ensures that the shopper can only choose from a range of payment methods.
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE paymentService PUBLIC "-//RBS
WorldPay//DTD RBS WorldPay PaymentService v1//EN"
"http://dtd.wp3.rbsworldpay.com/paymentService_v1.dtd"><paymentService
version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Servipag_Redirect_Order">
<description>jsredirect test order</description>
<amount value="1200000" currencyCode="CLP" exponent="2"/>
<![CDATA[
]]>
</orderContent>
<paymentMethodMask>
<include code="DINEROMAIL_SERVIPAG-SSL"/>
<include code="VISA-SSL"/>
</paymentMethodMask>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Avda. El Bosque Norte 99996</address1>
<address2>Las Condes</address2>
<address3></address3>
<postalCode>832000</postalCode>
<city>Santiago</city>
<state>Metropolitana de Santiago</state>
<countryCode>CL</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

In the above example, the inclusion of the specified payment method masks ensures that the
shopper can only choose from those payment methods on the WorldPay payment pages.
Because the firstName, lastName and telephoneNumber are provided, the shopper is not
prompted to enter any data on the WorldPay pages. The shopper only has to select the
payment method they want to use.

111

Alternative Payment Methods Guide

Example with Some Required Parameters
The following example shows an XML order where the merchant has supplied some of the
parameters required for this payment method. In the payment method mask, the merchant
has specified that the shopper can choose from any available payment method..
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE paymentService PUBLIC "-//RBS
WorldPay//DTD RBS WorldPay PaymentService v1//EN"
"http://dtd.wp3.rbsworldpay.com/paymentService_v1.dtd"><paymentService
version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Servipag_Redirect_Order_2">
<description>jsredirect test order</description>
<amount value="1200000" currencyCode="CLP" exponent="2"/>
<orderContent>
<![CDATA[
]]>
</orderContent>
<paymentMethodMask>
<include code="ALL"/>
</paymentMethodMask>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
<shippingAddress>
<address>
<firstName>Jos</firstName>
<lastName>Acosta</lastName>
<address1>Avda. El Bosque Norte 99996</address1>
<address2>Las Condes</address2>
<address3></address3>
<postalCode>832000</postalCode>
<city>Santiago</city>
<state>Metropolitana de Santiago</state>
<countryCode>CL</countryCode>
<telephoneNumber>0123456789</telephoneNumber>
</address>
</shippingAddress>
</order>
</submit>
</paymentService>

In the above example, the shopper can choose any available payment methods on the
WorldPay payment pages. The merchant has included data for the firstName and lastName;
the shopper is therefore not prompted to enter these on the WorldPay pages. However,
because the telephoneNumber is not included, the shopper must type this value on the
extra data page on the WorldPay payment pages.
Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns the pendingURL.
However, in some cases, the shopper might close the browser after completing the payment,
but before reaching the pending URL. In such cases, the payment may ultimately be
authorised.

112

About Testing the Integration

eKonto
eKonto is a real-time bank transfer payment method that a shopper can use to make an
online payment directly from their bank account. Payments are instantly debited from the
shoppers account and you receive immediate notification.
Shoppers can use this payment method only if they are registered for online banking with one
of the supported banks. Additionally, when making a payment, the shopper must authenticate
their bank account by using their login credentials.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Countries

Czech Republic

Acceptance Currency

CZK

Settlement to WorldPay
Currency

CZK

Minimum Amount for a Single

Transaction

5 CZK

Maximum Amount for a Single

Transaction

5,000 CZK

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

EKONTO-SSL

statementNarrative (Yes/No)

No

113

Alternative Payment Methods Guide

ePay
ePay is an eWallet that shoppers can use to pay utility bills or transfer money online.
Shoppers register their debit or credit card when signing up for an ePay account. Shoppers
can then make payment either directly from their eWallet, or from the credit or debit card
linked to their account.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Country

Bulgaria

Acceptance Currency

BGN

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 BGN

Maximum Amount for a Single

Transaction

5,000 BGN

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

EPAY-SSL

statementNarrative (Yes/No)

No

114

About Testing the Integration

Hal-Cash
Hal-Cash is an online bank transfer payment service operated by Telepay in Spain. This
payment method is used by over 20 million shoppers in Spain. When shopping online, the
shopper is provided with a unique purchase code, which the shopper can use to make the
payment online or by using mobile banking.

Transaction amounts must be in multiples of 10 EUR.

Payment Method Properties

The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Online bank transfer

Country

Spain

Acceptance Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

10 EUR

Maximum Amount for a Single

Transaction

600 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk

of chargeback to merchants.

Payment Method Mask

HALCASH-SSL

statementNarrative (Yes/No)

No

115

Alternative Payment Methods Guide

Konbini
Konbini is a post-pay voucher payment method offered by Digital Garage in Japan. Shoppers
can select their goods and services online, and then make payments at a local convenience
store. You can deliver your goods or services after you receive confirmation that the payment
has been made.
Convenience stores have a strong presence in Japan, which makes Konbini a suitable
payment method for merchants and shoppers. Digital Garage states that according to a
market research, Japanese online shoppers prefer cash-based payment methods. Because
Konbini is a cash-based method, shoppers are not required to have a bank account to use
this payment method.
To make a payment by using this method:
1. On the payment page, the shopper selects the Konbini payment method. The
shopper is redirected to the Digital Garage website, where they are presented with a
voucher.
2. The shopper prints the voucher and makes the payment at a convenience store.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Post-pay voucher

Country

Japan

Default Language and

Supported Language

ja

Acceptance Currency and

Preferred Currency

JPY

Settlement to WorldPay
Currency

JPY

Minimum Amount for a Single

Transaction

1 JPY

Maximum Amount for a Single

Transaction

63,000 JPY

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

116

About Testing the Integration

Payment Method Mask

KONBINI-SSL

statementNarrative (Yes/No)

No

Payment Delays and Status Changes

After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action

Delay

Payment Status

Notes

Shopper
chooses the
payment
method.

SHOPPER_REDIRECTED

The payment is created

in the
SHOPPER_REDIRECT
ED status.

Shopper makes
the payment.

Up to
10
days

The voucher expires

after 10 days.

Bank/PSP
authorises the
payment.

1 day

AUTHORISED

The payment is
authorised the next
working day.

The WorldPay
Payment
Service
captures the
payment.

Less
than
1
hour

CAPTURED

The WorldPay
Payment
Service clears
and settles this
payment
internally.

7
days

SETTLED

The WorldPay
Payment
Service settles
the payment to
you.

X
days

The settlement to you

occurs according to your
settlement cycle.

117

Alternative Payment Methods Guide

Konbini: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_Konbini_Order">
<description>test order</description>
<amount value="20" currencyCode="JPY" exponent="0"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<KONBINI-SSL shopperCountryCode="JP">
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</KONBINI-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

118

About Testing the Integration

PayU
PayU is an online bank transfer service that is supported by a number of banks in Poland.
When purchasing online, the shopper selects their preferred online bank and logs on to their
account to confirm payment. Real-time authorisation is returned for transactions that are
made during the banks working hours.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Online bank transfer

Country

Poland

Acceptance Currency

PLN

Settlement to WorldPay
Currency

PLN

Minimum Amount for a Single

Transaction

1 PLN

Maximum Amount for a Single

Transaction

5,000 PLN

Direct Refunds (Yes/No)

Yes.

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

PAYU-SSL

statementNarrative (Yes/No)

No

119

Alternative Payment Methods Guide

Przelewy24
Przelewy24 is a bank transfer service that is supported by a number of major banks in
Poland. Przelewy24 uses online bank authentication. When making a payment, the shopper
must authenticate their bank account by using their login credentials.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Real-time bank transfer

Country

Poland

Acceptance Currency

PLN

Settlement to WorldPay
Currency

PLN

Minimum Amount for a Single

Transaction

1 PLN

Maximum Amount for a Single

Transaction

5,000 PLN

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

PRZELEWY-SSL

statementNarrative (Yes/No)

No

120

About Testing the Integration

Qiwi
Qiwi is a payment method that shoppers based in Russia, Kazakhstan, and Ukarine can use
to make payments. Shoppers can use the following payment options:
Immediate payment by means of Qiwi eWallet. Shoppers can pay by using an
account or credit card registered in their eWallet.
Pay later by cash, at a Qiwi kiosk. Shoppers can create an invoice using their eWallet
account and pay cash at a Qiwi kiosk.
To use this payment method, shoppers must register for a Qiwi account and transfer funds
into or link a card with the account.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Countries

Russia, Kazakhstan, and Ukarine

Acceptance Currency

RUB and USD

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

500 USD

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk

of chargeback to merchants.

Payment Method Mask

QIWI-SSL

statementNarrative (Yes/No)

No

121

Alternative Payment Methods Guide

SafetyPay
SafetyPay is a global, secure Internet payment solution that is available in a number of
countries. Online banking shoppers can use SafetyPay to make online purchases from
merchants worldwide and pay directly through their local bank account in their local currency.
To make a payment by using this method:
1. On the payment page, the shopper selects the SafetyPay payment method. The
shopper is redirected to the SafetyPay website.
2. The shopper selects the bank that they want to use to complete the transaction. The
shopper is either:
Provided with instructions about how to complete the payment.
Redirected to their Internet bank.
Many banks authorise the transaction immediately. Some other banks might authorise the
transaction only during opening hours.
The shopper usually does not have to register with SafetyPay to use this method. However,
some banks require shoppers to declare their intention to use SafetyPay before making
payments by using this method.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Bank transfer

Countries

Austria, Brazil, Costa Rica, Mexico, Peru, Spain, and

United States

Acceptance Currencies

USD and EUR

Preferred Currency

EUR

Settlement to WorldPay
Currency

Settlement is in the same currency as the acceptance

currency.

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

5,000 USD

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

122

About Testing the Integration

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.
Payment Method Mask

SAFETYPAY-SSL

statementNarrative (Yes/No)

No

Payment Delays and Status Changes

After a shopper makes a payment, the payment status is likely to change according to the
following table.

These timelines are for guidance only. All references to days in the table imply
working days. Ensure that you account for the bank holidays in the PSP's country
and the merchant settlement country.

Action
Shopper
chooses the
payment
method.

Delay

Payment Status

Notes

SHOPPER_REDIRECTED

The payment is created

in the
SHOPPER_REDIRECT
ED status.
Some banks authorise
the payment
immediately, which
results in a real-time
notification to you.
Other banks authorise
the payment only during
working hours. If a
payment is submitted
during non-working
hours, it is not
authorised until the
opening hours of the
bank.

Shopper makes
the payment.

X
minutes

Bank/PSP
authorises the
payment.

0 days

AUTHORISED

The WorldPay
Payment
Service
captures the
payment.

Less
than 1
hour

CAPTURED

The WorldPay
Payment

6 days

SETTLED

123

Alternative Payment Methods Guide

Service clears
and settles this
payment
internally.
The WorldPay
Payment
Service settles
the payment to
you.

X days

The settlement to you

occurs according to your
settlement cycle.

SafetyPay: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_SafetyPay_Order">
<description>test order</description>
<amount value="1000" currencyCode="EUR" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<SAFETYPAY-SSL shopperCountryCode="AT">
<successURL>http://www.worldpay.com/sucessURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</SAFETYPAY-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

124

About Testing the Integration

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the bank has authorised the payment immediately (in real-time).
pendingURL, if the bank has accepted the payment, but the payment cannot be
authorised in real-time.

TeleIngreso
TeleIngreso is a payment method that shoppers can use to pay for goods and services online
by using offline payment methods including ATMs, post offices, and retail outlets.
TeleIngreso uses online bank authentication to produce a real-time notification of deposit.
When purchasing online, the shopper receives a 9-digit number that must be used when
making the payment at an ATM, a post office, or a retail outlet.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Post-pay voucher

Country

Spain

Acceptance Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 EUR

Maximum Amount for a Single

Transaction

5,000 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

TELEINGRESO-SSL

125

Alternative Payment Methods Guide

statementNarrative (Yes/No)

No

Real-Time Non-Hybrid APMs

When a shopper makes a payment by using a non-hybrid payment method, the PSP
completes the payment without prompting the shopper for any further information. The
payment pages of the PSP are therefore invisible to the shopper.
Payments that are made using real-time non-hybrid payment methods are authorised
immediately.

AstroPay Card
AstroPay Card is a virtual prepaid card that shoppers can use to make online payments.
To make a payment by using this method:
1. On the payment page, the shopper selects the AstroPay Card payment method.
2. The shopper types and confirms the required card details.
3. The transaction is authorised directly with the PSP in the background. The result of
the payment is returned to the shopper on the payment page.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay card

Countries

Brazil, Colombia, and Mexico

Acceptance Currency

USD

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 USD

Maximum Amount for a Single

Transaction

50,000 USD

Direct Refunds (Yes/No)

No

126

About Testing the Integration

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

ASTROPAYCARD-SSL

statementNarrative (Yes/No)

No

AstroPay Card: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_ToditoCash_Order">
<description>test order</description>
<amount value="100" currencyCode="USD" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<ASTROPAYCARD-SSL shopperCountryCode="MX">
<pan>1801114591360706</pan>
<cvv>3284</cvv>
<expiryDate><date year="2016" month="1"/></expiryDate>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</ASTROPAYCARD-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

127

Alternative Payment Methods Guide

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

pan

The AstroPay Card number.

cvv

The 3-digit Card Verification Value associated with the card.

The expiry date of the voucher in the following format:

date year="YYYY" month="MM"

expiryDate

For example:

date year="2016" month="1"

AstroPay Cards are valid until the last day of the month of expiry.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

128

About Testing the Integration

Moneta
Moneta is an eWallet that shoppers can use to make online payments. This payment method
is commonly used in countries where shoppers prefer cash-based payment methods.
To make a payment by using this method:
1. On the payment page, the shopper selects the Moneta payment method.
2. The shopper types and confirms the required account details.
3. The transaction is authorised directly with the PSP in the background. The result of
the payment is returned to the shopper on the payment page.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

eWallet

Countries

Armenia, Azerbaijan, Belarus, Georgia, Kazakhstan,

Kyrgyzstan, Moldova, Russia, Tajikistan,
Turkmenistan, Ukraine, and Uzbekistan

Acceptance Currencies

USD and EUR

Settlement to WorldPay
Currency

Payments made in RUB and USD are settled in USD.

Payments made in EUR are settled in EUR only.

Minimum Amount for a Single

Transaction

10 USD

Maximum Amount for a Single

Transaction

8,000 USD

Direct Refunds (Yes/No)

Yes

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

MONETA-SSL

statementNarrative

No

129

Alternative Payment Methods Guide

Moneta: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Moneta_Order'>
<description>Description here</description>
<amount currencyCode='USD' value='7500' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<MONETA-SSL shopperCountryCode='RU'>
<accountNumber>34127802</accountNumber>
<accountPassword>02534</accountPassword>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</MONETA-SSL>
</paymentDetails>
<shopper><shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

accountNumber

The shopper's Moneta account number.

The Moneta payment password that the shopper uses to confirm
payments.

accountPassword

Note: The accountPassword is not the account password that

the shopper uses to log in to the eWallet on the Moneta
website.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.

130

About Testing the Integration

After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

Swiff
Swiff is a prepaid voucher available in Canada. Shoppers can use this payment method to
purchase online securely. A shopper can purchase a Swiff voucher from a supporting outlet
and then spend it online.
To make a payment by using this method:
1. On the payment page, the shopper selects the Swiff payment method.
2. The shopper types and confirms the required voucher details.
3. The transaction is authorised directly with the PSP in the background. The result of
the payment is returned to the shopper on the payment page.
Payment Method Properties
The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay voucher

Country

Canada

Acceptance Currency and

Preferred Currency

CAD

Settlement to WorldPay
Currency

CAD

Minimum Amount for a Single

Transaction

1 CAD

Maximum Amount for a Single

Transaction

1,000 CAD

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

SWIFF-SSL

131

Alternative Payment Methods Guide

statementNarrative (Yes/No)

No

Swiff: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_swiff_Order'>
<description>Description here</description>
<amount currencyCode='CAD' value='1000' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<SWIFF-SSL shopperCountryCode='CA'>
<pan>2211000000000019</pan>
<cvv>111</cvv>
<expiryDate><date year="2016" month="1"/></expiryDate>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</SWIFF-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

pan

The 16-digit Swiff voucher number.

cvv

The 3-digit Card Verification Value associated with the card.

The expiry date of the voucher in the following format:

expiryDate
date year="YYYY" month="MM"

132

About Testing the Integration

For example:

date year="2016" month="1"

AstroPayCards are valid until the last day of the month of expiry.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

ToditoCash Card
ToditoCash card is a popular prepaid card service used in Mexico. The shopper purchases a
virtual voucher online or a physical card at a sales outlet and then uses the voucher/card for
purchasing goods and services online. Both the voucher and card function in the same way,
and have a card number and a PIN. The shopper can top up the voucher or card by using
cash or other means.
To make a payment by using this method:
1. On the payment page, the shopper selects the ToditoCash payment method.
2. The shopper types and confirms the required card details.
3. The transaction is authorised directly with the PSP in the background. The result of
the payment is returned to the shopper on the payment page.

133

Alternative Payment Methods Guide

Payment Method Properties

The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Pre-pay voucher

Country

Mexico

Acceptance Currency

MXN

Settlement to WorldPay
Currency

USD

Minimum Amount for a Single

Transaction

1 MXN

Maximum Amount for a Single

Transaction

5,000 MXN

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

TODITOCASH-SSL

statementNarrative

No

134

About Testing the Integration

ToditoCash Card: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//EN"
"http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="XXXX">
<submit>
<order orderCode="Example_ToditoCash_Order">
<description>test order</description>
<amount value="500" currencyCode="MXN" exponent="2"/>
<orderContent>
<![CDATA[]]>
</orderContent>
<paymentDetails>
<TODITOCARD-SSL shopperCountryCode="MX">
<pan>1111111111</pan>
<pin>3333</pin>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</TODITOCARD-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

pan

The voucher/card number.

pin

The Personal Identification Number corresponding to the card.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.

135

Alternative Payment Methods Guide

After you submit your order, the WorldPay Payment Service returns either of the following
response URLs:
successURL, if the payment is successful.
pendingURL, which is returned in exceptional circumstances, for example, if there is
an unexpected delay in the bank authorising the payment.

Delayed Non-Hybrid APMs

When a shopper makes a payment by using a delayed non-hybrid payment method, the PSP
completes the payment without prompting the shopper for any further information. The
payment pages of the PSP are therefore invisible to the shopper.
Delayed non-hybrid payments are not authorised immediately. Funds are transferred into
your account depending on the payment processing policies of the PSP.

Multibanco
Multibanco is an interbank network in Portugal. This network is run by SIBS (Sociedade
Interbancria de Servios S.A.) and enables many services, including payment services, to
be hosted.
Shoppers can use the Multibanco payment method to pay merchants through their Internet
bank or by using an ATM. The service is supported by all major banks in Portugal, and is
therefore accessible to the maximum number of shoppers.

Multibanco is different from other APMs in the following ways:

This payment method does not support the default pending URL.
You must always supply your own URLs.

The pending URL is always returned with the data appended to it,
which you must display to the shopper. For more information, see
Example XML Order.

To make a payment by using this method:

1. On the payment page, the shopper selects the Multibanco payment method. The
payment pages then display a payment reference and other details which the
shopper can use to make a payment from his internet banking application, or via an
ATM using their bank card.
2. The shopper makes the payment by either logging on to their online bank, or using
an ATM.

136

About Testing the Integration

Payment Method Properties

The properties for this payment method are described in the following table.

Property

Description/Value

Payment Type

Post-pay voucher

Country

Portugal

Acceptance Currency and

Preferred Currency

EUR

Settlement to WorldPay
Currency

EUR

Minimum Amount for a Single

Transaction

1 EUR

Maximum Amount for a Single

Transaction

400 EUR

Direct Refunds (Yes/No)

No

Chargebacks (Yes/No)

Yes. Payments are not guaranteed and a

chargeback/dispute process is available to shoppers.
There is a risk of chargeback to merchants.

Payment Method Mask

MULTIBANCO-SSL

statementNarrative (Yes/No)

No

137

Alternative Payment Methods Guide

MultiBanco: Example XML Order

Example: Direct Model
The following example shows an XML order for the direct integration model.
<?xml version='1.0' ?>
<!DOCTYPE paymentService PUBLIC '-//WorldPay//DTD WorldPay PaymentService v1//EN'
'dtd/paymentService_v1.dtd'>
<paymentService merchantCode='XXXX' version='1.4'>
<submit>
<order orderCode='Example_Multibanco_Order'>
<description>Description here</description>
<amount currencyCode='EUR' value='100' exponent='2'/>
<orderContent>Order Content Here</orderContent>
<paymentDetails>
<MULTIBANCO-SSL shopperCountryCode='PT'>
<successURL>http://www.worldpay.com/successURL</successURL>
<cancelURL>http://www.worldpay.com/cancelURL</cancelURL>
<pendingURL>http://www.worldpay.com/pendingURL</pendingURL>
</MULTIBANCO-SSL>
</paymentDetails>
<shopper>
<shopperEmailAddress>[email protected]</shopperEmailAddress>
</shopper>
</order>
</submit>
</paymentService>

Mandatory Data
The following table lists the mandatory data that you must include in your order.

Parameter Name

Description

shopperEmailAddress

The email address of the shopper.

Response URLs
If you are using the direct model, you must specify the successURL, cancel URL, and
pending URL. If you are using the redirect model, we recommend that you specify these
URLs.
After you submit your order, the WorldPay Payment Service returns the following response:
Direct model: The pending URL is returned. Information about how to complete the
payment is returned to the shopper on the WorldPay payment pages.
Redirect model: The pending URL is returned. However, additional information is
added to the response URL, as shown in the following example:
http://www.worldpay.com/pendingURL?orderKey=BIBIT^DEMO^Example_Multibanco_Order&st
atus=OPEN&multibancoReference=726+092+065&multibanco
Entity=11249&multibancoPaymentAmount=100&multibancoPaymentCurrency=EUR

138

About Testing the Integration

This example response includes the parameters listed in the following table.

Parameter

Example

Description

multibancoReference

726+092+065

The payment reference that the

shopper must use to complete
the payment.

multibancoEntity

11249

The entity reference that the

shopper must use to complete
the payment.

PaymentAmount

100

The amount that the shopper

should pay, expressed in minor
currency units. For example,
100 = 100 Euro cents.

multibancoPaymentCurrency

EUR

The currency corresponding to

the PaymentAmount.

In the above example, the merchant must display a message of the following form to the
shopper:
To complete your payment, please make a deposit using the details below. To avoid
delays in your payment being processed, please ensure that you use the exact
details and payment amount shown below. You can pay through your Internet bank or
at an ATM.
Reference: 726092065
Entity: 11249
Amount: EU

139

Alternative Payment Methods Guide

About Testing APM Transactions

You can test your technical integration by using Sandbox, which is a comprehensive securetest system offered by WorldPay. The Sandbox system simulates a production experience,
but in a shielded secure-test environment.
You can currently use the Sandbox system to test card payments. You can submit orders and
test the payment life cycle from initial order submission through to the SETTLED status. The
Sandbox system is also expected to support a subset of APMs in future, where you can
submit test payments for APMs and test the payment cycle up to and including the
CAPTURED status. For more information, see the Sandbox User Guide.

140

About Refunding Payments

All payments made by using APMs can be refunded within 60 days from the date the
payment was authorised. Depending on your business requirements, you can:
Refund a payment either partially or completely.
Refund a payment through the Payment Service Provider (PSP), where possible.
Refund a payment manually by making a bank transfer, for example, if the original
payment method does not support refunds or if attempts to refund a payment through
the PSP have failed.

Scope
You can refund payments made using any APM. However, the refund options that you can
use primarily depend on the type of payment method used.
For information about the various methods or options that you can use to refund payments
and the list of payment methods supported by each refund method, see the Refunding
Alternative Payments Guide.

Fraud and Risk Management

Each refund is always associated with the original transaction. The total value of a refund is
restricted to no more than the original payment value in the appropriate shopper currency.
To further minimise the risk of fraud and money laundering, WorldPay performs a number of
checks to ensure that:
Refund requests have originated from an authorised and verified source.
Refund requests have been initiated only by the merchant related to the original
payment.
Additionally, WorldPay monitors potential fraud by identifying payments that have been
refunded by means of a different payment method than the original payment.

Tracking and Audit Control

After you have initiated a refund, you can track its status by using the MI. Additionally, you
can generate reports for tracking and audit purposes.
For more information, see the Refunding Alternative Payments Guide.

141

Alternative Payment Methods Guide

This page is intentionally blank.

142

APM Quick Reference

Real-Time Hybrid Payment Methods
The following table summarises the real-time hybrid payment methods.

Country

Acceptance
Currency

Settlement
to
WorldPay
Currency

Min
Amount

Max
Amount

Direct
Refunds
(Y/N)

Chargebacks
(Y/N)

Payment Method
Mask

Internet
banking

China

CNY

USD

1 CNY

750 CNY

NINETYNINEBILL
-SSL

Abaqoos

eWallet
and Prepay
voucher

Hungary

HUF

HUF

No
minimum

500,000
HUF

ABAQOOS-SSL

AGMO

Realtime
bank
transfer

Czech
Republic

CZK

CZK

10 CZK

50,000
CZK

AGMO-SSL

Payment
Method

Type

99Bill

143

Alternative Payment Methods Guide

Settlement
is in the
same
currency as
the
acceptance
currency

No
minimum

No
maximum

ALIPAY-SSL

Alipay

eWallet

China

AUD, CAD,
CHF, DKK,
EUR, GBP,
HKD, NOK,
SEK, SGD,
and USD

BankAxess

Realtime
bank
transfer

Norway

NOK

NOK

1 NOK

50,000
NOK

BANKAXESSSSL

Banklink
NORDEA

Realtime
bank
transfer

Latvia

LVL and
EUR

EUR

No
minimum

10,000
LVL

BANKLINKNORD
EA-SSL

BillingPartner

Realtime
bank
transfer

Germany

EUR

EUR

No
minimum

5,000
EUR

BILLINGPARTNE
R-SSL

144

APM Quick Reference

CashU

eWallet

Bahrain,
Canada,
Egypt, Israel,
Jordan,
Kuwait,
Lebanon,
Malaysia,
Mauritania,
Morocco,
Oman, Qatar,
Russia, Saudi
Arabia,
Tanzania,
Tunisia,
Turkey,
Ukraine,
United Arab
Emirates,
Uruguay, and
Venezuela

Euteller

Realtime
bank
transfer

Finland

EUR

EUR

1 EUR

10,000
EUR

EUTELLER-SSL

eWireDK

eWallet

Denmark

DKK

DKK

5 DKK

3,000
DKK

EWIREDK-SSL

eWireNO

eWallet

Norway

NOK

NOK

5 NOK

1,000
NOK

EWIRENO-SSL

eWireSE

eWallet

Sweden

SEK

SEK

5 SEK

1,000 SEK

EWIRESE-SSL

USD

USD

1 USD

3,200
USD

CASHU-SSL

145

Alternative Payment Methods Guide

InstaDebit

Bank
Transfer

Canada

CAD and
USD

Settlement
is in the
same
currency as
the
acceptance
currency

Mister Cash

Debit
card

Belgium

EUR

EUR

No
minimum

5,000
EUR

MISTERCASHSSL

NeoSurf

Pre-pay
voucher

Belgium,
France, Italy,
and Spain

EUR

EUR

No
minimum

50,000
EUR*

NEOSURF-SSL

Paga Verve

Debit
card

Nigeria

USD

USD

1 USD

620 USD

PAGA_VERVESSL

Paga Wallet

eWallet

Nigeria

USD

USD

1 USD

620 USD

PAGA-SSL

1 USD

50,000
USD

INSTADEBIT-SSL

146

APM Quick Reference

PaySafeCard

Pre-pay
card

Austria,
Belgium,
Cyprus,
Czech
Republic,
Denmark,
France,
Germany,
Greece,
Ireland, Italy,
Liechtenstein,
Luxembourg,
Netherlands,
Norway,
Poland,
Portugal,
Romania,
Slovakia,
Slovenia,
Spain,
Sweden,
Switzerland,
and United
Kingdom

POLi

Realtime
bank
transfer

Australia

AUD

AUD

No
minimum

501 AUD

POLI-SSL

POLiNZ

Realtime
bank
transfer

New Zealand

NZD

NZD

1 NZD

501 NZD

POLINZ-SSL

CHF, CZK,
DKK, EUR,
RON, GBP,
NOK, PLN,
SEK, and
USD

CHF

No
minimum

10,000
EUR

PAYSAFECARDSSL

147

Alternative Payment Methods Guide

PostePay

Pre-pay
card

Italy

EUR

EUR

1 EUR

1,000
EUR

POSTEPAY-SSL

SOFORT
Banking

Realtime
bank
transfer

Austria,
France, and
Germany

EUR

EUR

No
minimum

2,000
EUR

SOFORT-SSL

Sporopay

Realtime
bank
transfer

Slovakia

EUR

EUR

1 EUR

500 EUR

SPOROPAY-SSL

Ticket Premium

Pre-pay
card

France

EUR

EUR

1 EUR

5,000
EUR

TICKETSURFSSL

No
minimum

5,000 CZK

TRUSTPAY_CZSSL

No
minimum

5,000
EUR

TRUSTPAY_EESSL

TrustPayCZ

Realtime
bank
transfer

Czech
Republic

EUR and
CZK

Settlement
is in the
same
currency as
the
acceptance
currency

TrustPayEE

Realtime
bank
transfer

Estonia

EUR

EUR

148

APM Quick Reference

TrustPaySK

WebMoney

Yandex.Money

Realtime
bank
transfer

Slovakia

EUR

EUR

No
minimum

5,000
EUR

TRUSTPAY_SKSSL

eWallet

Armenia,
Azerbaijan,
Belarus,
China,
Georgia,
Kazakhstan,
Kyrgyzstan,
Latvia,
Lithuania,
Moldova,
Russia,
Tajikistan,
Turkmenistan,
Ukraine, and
Uzbekistan

RUB, USD,
and EUR

USD

10 USD

2,000
USD

WEBMONEY-SSL

eWallet

Armenia,
Azerbaijan,
Belarus,
Georgia,
Kazakhstan,
Kyrgyzstan,
Moldova,
Russia,
Tajikistan,
Turkmenistan,
Ukraine, and
Uzbekistan

RUB and
USD

USD

1 USD

640 USD

YANDEX.MONEY
-SSL

149

Alternative Payment Methods Guide

* NeoSurf: In practice, the maximum amount is EUR 100, which is the maximum value of a single voucher. Because shoppers can consolidate multiple
vouchers, the maximum amount can be slightly more than EUR 100.

150

APM Quick Reference

Delayed Hybrid Payment Methods

The following table summarises the delayed hybrid payment methods.

Country

Acceptance
Currency

Settlement
to
WorldPay
Currency

Min
Amount

Max
Amount

Direct
Refunds
(Y/N)

Chargebacks
(Y/N)

Payment Method
Mask

Postpay
voucher

Colombia

COP

USD

5,000 COP

500,000
COP

BALOTO-SSL

Boleto
Bancrio

Postpay
voucher

Brazil

BRL

USD

18 BRL

6,400 BRL

BOLETO-SSL

DineroMail
7eleven

Postpay
voucher

Mexico

MXN

USD

20 MXN

20,000
MXN

DINEROMAIL_
7ELEVEN-SSL

DineroMail
Oxxo

Postpay
voucher

Mexico

MXN

USD

20 MXN

20,000
MXN

DINEROMAIL_
OXXO-SSL

DineroMail
Bank
Transfer

Offline
bank
transfer

Mexico

MXN

USD

20 MXN

31,000
MXN

DINEROMAIL_
ONLINE_BT-SSL

Payment
Method

Type

Baloto

151

Alternative Payment Methods Guide

DineroMail
ServiPag

Postpay
voucher

Chile

CLP

USD

1,200 CLP

750,000
CLP

DINEROMAIL_
SERVIPAG-SSL

eKonto

Realtime
bank
transfer

Czech
Republic

CZK

CZK

5 CZK

5,000 CZK

EKONTO-SSL

ePay

eWallet

Bulgaria

BGN

EUR

1 BGN

5,000
BGN

EPAY-SSL

Hal-Cash

Online
bank
transfer

Spain

EUR

EUR

10 EUR

600 EUR

HALCASH-SSL

Konbini

Postpay
voucher

Japan

JPY

JPY

1 JPY

63,000
JPY

KONBINI-SSL

PayU

Online
bank
transfer

Poland

PLN

PLN

1 PLN

5,000 PLN

PAYU-SSL

Przelewy24

Realtime
bank
transfer

Poland

PLN

PLN

1 PLN

5,000 PLN

PRZELEWY24-SSL

152

APM Quick Reference

eWallet

Russia,
Kazakhstan,
and Ukarine

RUB and
USD

USD

1 USD

500 USD

QIWI-SSL

SafetyPay

Bank
Transfer

Austria,
Brazil, Costa
Rica,
Mexico,
Peru, Spain,
and United
States

USD and
EUR

EUR

1 USD

5,000 USD

SAFETYPAY-SSL

TeleIngreso

Postpay
voucher

Spain

EUR

EUR

1 EUR

5,000 EUR

TELEINGRESOSSL

Qiwi

153

Alternative Payment Methods Guide

Real-Time Non-Hybrid Payment Methods

The following table summarises the real-time non-hybrid hybrid payment methods.

Payment
Method

Type

AstroPay Card

Pre-pay
card

Country

Acceptance
Currency

Settlement
to
WorldPay
Currency

Min
Amount

Max
Amount

Direct
Refunds
(Y/N)

Chargebacks
(Y/N)

Payment
Method Mask

Brazil,
Colombia, and
Mexico

USD

USD

1 USD

50,000
USD

ASTROPAYCA
RD-SSL

USD and
EUR

Payments
made in
RUB and
USD are
settled in
USD.
Payments
made in
EUR are
settled in
EUR only.

10 USD

8,000
USD

MONETA-SSL

CAD

CAD

1 CAD

1,000
CAD

SWIFF-SSL

Armenia,
Azerbaijan,
Belarus,
Georgia,
Kazakhstan,
Kyrgyzstan,
Moneta

eWallet

Moldova,
Russia,
Tajikistan,
Turkmenistan,
Ukraine, and
Uzbekistan

Swiff

Pre-pay
voucher

Canada

154

APM Quick Reference

Toditocash
Card

Pre-pay
voucher

Mexico

MXN

USD

1 MXN

5,000
MXN

TODITOCASHSSL

155

Alternative Payment Methods Guide

Delayed Non-Hybrid Payment Methods

The following table summarises the delayed non-hybrid payment methods.

Payment
Method

Multibanco

Type

Post-pay
voucher

Country

Portugal

Acceptance
Currency

EUR

Settlement
to WorldPay
Currency

Min
Amount

EUR

1 EUR

Max
Amount

400 EUR

Direct
Refunds
(Y/N)

Chargebacks
(Y/N)

Payment
Method Mask

MULTIBANCOSSL

156