Links

Defining the proxy scheme in Nexus

Once the PLSO has signed a bilateral agreement with the relevant IPSO, the PLSO must provide reference data to Nexus (via the IPSO).
This reference data defines the proxy lookup scheme and the proxy formats that it supports. The data will be provided to PSPs who are sending payments to the PLSO’s country. The PLSO is responsible for ensuring that the data is kept up to date.

TABLE: Proxy scheme information

ELEMENT
FORMAT
USAGE
Scheme Name
Max35Text
Name of the proxy scheme
Effective Date
ISODateTime
Date when this version of the scheme definition takes effect (used to manage updates)
Operating Countries
List of ISO-3166 alpha-2 country codes
List of countries in which this proxy scheme is available
Proxy Formats
List of proxy formats – see table below
List of the different types of proxy used in this proxy scheme

Defining individual proxy formats

For each proxy format, the following fields are defined:
ELEMENT
FORMAT
USAGE
Proxy Type
4 letters
The Proxy Type in Nexus is taken from the ISO 20022 External Code Set (available at www.iso20022.org) using the values from ExternalProxyAccountType1Code. The code can be mapped to a description in the language used in the PSP’s app. Current values are shown below, with the most commonly used types in bold.
Proxy Format
Regular expression
To be used for client-side validation in the PSP’s app or online banking services
Proxy Example
Text
Can be used as the “placeholder” element in a HTML form
Proxy Description
Text
Can be used as a tooltip or sub-label in the HTML form. An English-language description is mandatory, and other language descriptions can be defined. More specific description of the type of data required for this proxy type. For example, for a proxy type NIDN (National Identify Number) for Singapore, the description may include “NRIC/FIN” – two national identity number types).

Proxy type codes used in Nexus (ExternalProxyAccountType1Code)

The following codes are ExternalProxyAccountType1Code from the ISO 20022 External Code Set, available at www.iso20022.org. Commonly used proxy types are highlighted in bold.
A PLSO must use these codes when defining its scheme and when communicating with Nexus. If different codes are used domestically, it must map those codes to the list below.
PROXY TYPE CODE
TYPE OF PROXY
BIID
Biller Subscriber Identification
CINC
Certificate of Incorporation Number
COTX
Corporate Tax Identification
COID
Country Autonomy Identification
CUST
Customer identification Number
DNAM
Domain Name (Internet)
DRLC
Driver License Number
EIDN
Electronic Identification
EMAL
Email address
EWAL
E-Wallet identification
PVTX
Individual tax identification
LEIC
Legal Entity Identifier Code
MBNO
Mobile phone number
NIDN
National identification number
CCPT
Passport number
SHID
Scheme identification Number
SOSE
Social Security Number
TELE
Telephone Number (land line)
UBIL
Utilities Subscription Identification
VIPN
Vehicle Identification Plate Number
TOKN
Virtual payment addresses (treated as a “token”)

Example proxy scheme definition

Below is an example proxy scheme definition, in this case for the PayNow service in Singapore. Note only three of the proxy types used in PayNow are shown below.
Example proxy scheme definition (click to expand)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<PrxySchmes xmlns="https://nexus.bisih.org/nexus.001.001.01">
<PrxySchme>
<OprtngCtrys>
<Ctry>SG</Ctry>
</OprtngCtrys>
<EffctvDtTm>2022-04-21T00:25:04.258+05:30</EffctvDtTm>
<SchmeNm>PayNow</SchmeNm>
<PrxyFmts>
<Prxy>
<PrxyTp>MBNO</PrxyTp>
<PrxyExmpl>+6581234567</PrxyExmpl>
<PrxyFmt>^\+65\d{8}$</PrxyFmt>
<PrxyDesc>Any Singaporean mobile number</PrxyDesc>
</Prxy>
<Prxy>
<PrxyTp>NIDN</PrxyTp>
<PrxyExmpl>640829075377</PrxyExmpl>
<PrxyFmt>^\d{12}$</PrxyFmt>
<PrxyDesc>Any Singaporean company/individual government ID</PrxyDesc>
</Prxy>
<Prxy>
<PrxyTp>CINC</PrxyTp>
<PrxyExmpl>T09LL0001B</PrxyExmpl>
<PrxyFmt>^[A-Za-z0-9]{9,10}$</PrxyFmt>
<PrxyDesc>Unique Entity Number (UEN)</PrxyDesc>
</Prxy>
</PrxyFmts>
</PrxySchme>
</PrxySchmes>