Specifications of the online player verification service for gaming operators (SVJ-WS)

STATE SECRETARIAT FOR FINANCE Online Player Verification Service DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING Specifications of the online pl

15 downloads 105 Views 3MB Size

Story Transcript

STATE SECRETARIAT FOR FINANCE

Online Player Verification Service

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Specifications of the online player verification service for gaming operators (SVJ-WS)

Version 1.8 APRIL 2015

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

1

Objectives .................................................................................................................. 8

1.1 1.2

2

Web service and operations............................................................................... 15

Input parameters ................................................................................................ 19

2.2.1

VerifyPlayer, VerifyRGIAJ and VerifyIdentity .............................................. 19

2.2.2

Parameters VerifyChangesRGIAJ .............................................................. 25

2.2.3

Parameters removePlayer .......................................................................... 25

2.3

Responses of the service ................................................................................... 26

2.3.1

Response to VerifyPlayer ........................................................................... 26

2.3.2

Response to VerifyRGIAJ ........................................................................... 27

2.3.3

Response to VerifyIdentity .......................................................................... 28

2.3.4

Response to VerifyChangesRGIAJ............................................................. 28

2.3.5

Response to removePlayer......................................................................... 29

2.4

Authentication of the Operator ........................................................................... 29

Description of the environments ........................................................................... 34

3.1 3.2

4

Monitoring changes in the document ................................................................... 9

Schedule for implementing the new endpoints................................................... 14

Functional specifications ....................................................................................... 15

2.1 2.2

3

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

Production.......................................................................................................... 34

Tests .................................................................................................................. 35

Appendices.............................................................................................................. 35

4.1 4.2

Result and error codes....................................................................................... 35

Trial games in the testing environment .............................................................. 38

4.2.1

Description of the test cases ....................................................................... 38

4.2.2

List of generic error cases........................................................................... 44

4.2.2.1 Missing Mandatory Information ............................................................... 44

4.2.2.2 Authentication of the Operator................................................................. 44

4.2.2.3 Repeated DNI or NIE .............................................................................. 44

4.2.2.4 Validation of DNI/NIE format ................................................................... 44

2 of 132

CAPITÁN HAYA, 53 – 6th floor

28071 - MADRID

TEL. +34 91 596 26 14

FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

4.2.2.5 Validation of the DNI/NIE letter................................................................ 45

4.2.2.6 Validation of Surname2, mandatory for an NIF ....................................... 45

4.2.2.7 Validation of date of birth after 01/01/1900.............................................. 45

4.2.2.8 Invalid characters check .......................................................................... 45

4.2.2.9 The RGIAJ server is unavailable ............................................................. 45

4.2.2.10

The SVDI server is not available.......................................................... 45

4.2.2.11

Validation of the support number format .............................................. 45

4.2.2.12

Validation of support number with NIF ................................................. 46

4.2.3

Test Cases for the verifyPlayer operation ................................................... 46

4.2.3.1 Verify a player NOT OK- IN RGIAJ ......................................................... 46

4.2.3.2 Verify a player OK- IN RGIAJ .................................................................. 46

4.2.3.3 Verify two players OK- NOT IN RGIAJ .................................................... 47

4.2.3.4 Verify two players, one OK- NOT IN RGIAJ and another with FORMAT ERROR 49 4.2.3.5 Verify two players, both OK- IN RGIAJ.................................................... 50

4.2.3.6 Verify a player OK- NOT IN RGIAJ ......................................................... 51

4.2.3.7 Verify a player OK- NOT IN RGIAJ (but a minor) .................................... 52

4.2.3.8 Verify a player with an Annulled NIF- NOT IN RGIAJ.............................. 53

4.2.3.9 Verify a player with a Withdrawn NIF- NOT IN RGIAJ............................. 54

4.2.3.10

Verify a player missing mandatory information .................................... 54

4.2.3.11

Verify a player OK- IN RGIAJ .............................................................. 55

4.2.3.12

Verify a player without sending a date of birth ..................................... 56

4.2.3.13

Verify a player that is NOT OK– NOT IN RGIAJ .................................. 56

4.2.3.14

Verify the same ID two times in the same request............................... 57

4.2.3.15

Verify a player with an NIE and support number.................................. 58

3 of 132

CAPITÁN HAYA, 53 – 6th floor

28071 - MADRID

TEL. +34 91 596 26 14

FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

4.2.3.16

Verify a player with an NIE and support number with incorrect format 62

4.2.3.17

Verify a player with a DNI, sending support number............................ 63

4.2.4

Test Cases for the verifyIdentity operation.................................................. 64

4.2.4.1 Verify an identity OK................................................................................ 64

4.2.4.2 Verify an identity Not OK ......................................................................... 64

4.2.4.3 Verify an identity with FORMAT ERROR ................................................ 65

4.2.4.4 Verify an identity that is incorrectly identified........................................... 66

4.2.4.5 Verify identity of Annulled NIF ................................................................. 66

4.2.4.6 Verify a player with a Withdrawn NIF ...................................................... 67

4.2.4.7 Verify a player with an NIE and support number ..................................... 68

4.2.4.8 Verify a player with an NIE and support number with incorrect format .... 70 4.2.4.9 Verify a player with a DNI, sending support number ............................... 71

4.2.5

Test Cases for the verifyRGIAJ Operation .................................................. 72

4.2.5.1 Verify a player registered in the RGIAJ ................................................... 72

4.2.5.2 Verify a player not registered in the RGIAJ ............................................. 72

4.2.5.3 Verify a player registered in RGIAJ but without sending all the information 73 4.2.5.4 Verify a player not registered in the RGIAJ ............................................. 74 4.2.5.5 Verify a RGIAJ with FORMAT ERROR ................................................... 75 4.2.5.6 Verify a player with an NIE and support number with incorrect format .... 76 4.2.5.7 Verify a player with a DNI, sending support number ............................... 77

4.2.6

Test Cases for the verifyChangesRGIAJ Operation.................................... 78

4.2.6.1 Verify changes in RGIAJ without verifying players .................................. 79

4.2.6.2 Verify changes in RGIAJ upon verifying players...................................... 79

4.2.7

Test Cases for the removePlayer operation................................................ 81

4 of 132

CAPITÁN HAYA, 53 – 6th floor

28071 - MADRID

TEL. +34 91 596 26 14

FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

4.2.7.1 Removing a player added by the Operator.............................................. 81

4.2.7.2 Removing a player not previously added by the Operator....................... 81

4.2.7.3 Removing a player previously removed by the Operator......................... 82

4.2.7.4 Incorrect reason for removal.................................................................... 82

4.2.7.5 Removing a player sending an incorrect DNI/NIE ................................... 83

4.2.7.6 Removing a player without sending a DNI/NIE........................................ 84

4.2.7.7 Removing a player without sending the reason....................................... 84

4.2.7.8 Verify changes in the RGIAJ after a removal........................................... 85

4.3

Trial games to verify the production environment .............................................. 87

4.3.1

List of generic error cases........................................................................... 87

4.3.1.1 Blank mandatory data fields .................................................................... 87

4.3.1.2 Authentication of the Operator................................................................. 87

4.3.1.3 Validation of DNI/NIE format ................................................................... 87

4.3.1.4 Validation of the DNI/NIE letter................................................................ 88

4.3.1.5 Validation of Surname2, mandatory for an NIF ....................................... 88

4.3.1.6 Validation of date of birth after 01/01/1900.............................................. 88

4.3.1.7 Validation of invalid characters................................................................ 88

4.3.1.8 Repeated DNI or NIE .............................................................................. 88

4.3.2

Test Cases for the verifyPlayer operation ................................................... 89

4.3.2.1 Verify a player NOT OK-NOT IN RGIAJ.................................................. 89

4.3.2.2 Verify a player OK- IN RGIAJ .................................................................. 90

4.3.2.3 Verify two players OK- NOT IN RGIAJ .................................................... 91

4.3.2.4 Verify two players, one OK- NOT IN RGIAJ and another with FORMAT

ERROR 92

4.3.2.5 Verify two players, both OK- IN RGIAJ.................................................... 93

5 of 132

CAPITÁN HAYA, 53 – 6th floor

28071 - MADRID

TEL. +34 91 596 26 14

FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

4.3.2.6 Verify a player OK- NOT IN RGIAJ ......................................................... 95

4.3.2.7 Verify a player NOT OK- IN RGIAJ ......................................................... 96

4.3.2.8 Verify a player OK- NOT IN RGIAJ (but a minor) .................................... 97

4.3.2.9 Verify a player missing mandatory information........................................ 97

4.3.2.10

Verify a player OK- IN RGIAJ .............................................................. 98

4.3.2.11

Verify a player without sending a date of birth ................................... 100

4.3.2.12

Verify a player for which NO DNI EXISTS ......................................... 101

4.3.2.13

Verify a player that returns a Service error (COD005) ....................... 102

4.3.2.14

Verify the same DNI two times in the same request .......................... 103

4.3.3

Test Cases for the verifyIdentity operation................................................ 104

4.3.3.1 Verify an identity OK but not of legal age .............................................. 104

4.3.3.2 Verify an identity OK.............................................................................. 105

4.3.3.3 Verify an identity Not OK ....................................................................... 105

4.3.3.4 Verify an identity Not OK ....................................................................... 106

4.3.3.5 Verify an identity with FORMAT ERROR .............................................. 107

4.3.3.6 Verify an identity with invalid characters................................................ 108

4.3.3.7 Verify an identity that DOES NOT EXIST .............................................. 109

4.3.3.8 Verify an identity that returns a Service error (COD005) ....................... 109

4.3.4

Test Cases for the verifyRGIAJ Operation ................................................ 111

4.3.4.1 Verify a player registered in the RGIAJ ................................................. 111

4.3.4.2 Verify a player not registered in the RGIAJ ........................................... 111

4.3.4.3 Verify a player registered in RGIAJ but without sending all the information

112

4.3.4.4 Verify a player not registered in the RGIAJ ........................................... 113

4.3.4.5 Verify a RGIAJ with FORMAT ERROR ................................................. 114

6 of 132

CAPITÁN HAYA, 53 – 6th floor

28071 - MADRID

TEL. +34 91 596 26 14

FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

4.3.5

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

Test Cases for the verifyChangesRGIAJ Operation.................................. 115

4.3.5.1 Verifychanges in RGIAJ without verifying players ................................. 116

4.3.5.2 Verifychanges in RGIAJ upon verifying players..................................... 117

4.3.6

Test Cases for the removePlayer operation.............................................. 119

4.3.6.1 Removing a player added by the Operator............................................ 119

4.3.6.2 Removing a player not previously added by the Operator..................... 119 4.3.6.3 Removing a player previously removed by the Operator....................... 120 4.3.6.4 Incorrect reason for removal.................................................................. 121 4.3.6.5 Removing a player sending an incorrect DNI/NIE ................................. 121 4.3.6.6 Removing a player without sending a DNI/NIE...................................... 122 4.3.6.7 Removing a player without sending the reason..................................... 123 4.3.6.8 Verify changes in the RGIAJ after a removal......................................... 123 4.4 5

Request for registration in the service.............................................................. 124

Testing of the service ........................................................................................... 126 5.1 5.2 5.3 5.4 5.5

Objectives ........................................................................................................ 126 Functional specifications .................................................................................. 126 Description of the system................................................................................. 126 Secure connection ........................................................................................... 126 Check requests from a browser. ...................................................................... 127

5.5.1

Web application ........................................................................................ 127

5.5.2

Through GET requests using the HTTPS protocol.................................... 127

5.6

Responses from the TEST service (TESTOPERATORS)................................ 128

5.6.1

In web format. ........................................................................................... 128

5.6.2

GET petitions using the HTTPS protocol .................................................. 129

5.7 5.8 5.9 5.10

Example for using the TESTOPERATORS service from a Java client............. 129

Requirements................................................................................................... 131

Examples: ........................................................................................................ 131

Couplings ......................................................................................................... 131

7 of 132

CAPITÁN HAYA, 53 – 6th floor

28071 - MADRID

TEL. +34 91 596 26 14

FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

1 Objectives This document describes the technical and functional specifications of the online player verification service which the DGOJ will offer the different gaming operators to verify the identification data of residents in Spain in real time, in compliance with Article 26.3 of Royal Decree 1613/2011, of 14 November, implementing Law 13/2011 of 27 May on the regulation of gaming, regarding the technical requirements of gaming activities. Together with the identification data, the date of birth of the player will also be checked to enable the operator to verify the participant is of legal age, as set out in Article 27.3 of the same Royal Decree. Finally, these web services will provide the procedures referred to in Article 27.2 to give operators telematic access to the General Register of Gaming Access Bans (RGIAJ) before activating the user account of the participant, and to later regularly check the data of the user accounts against the RGIAJ. To enable the implementation of the software client which will use these web services, the Directorate General for the Regulation of Gambling will provide operators with a test environment and test games described in this document, and the form for requesting registration for the service.

8 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

1.1 Monitoring changes in the document Version Date

Description

0.1

SEP 2011

Initial version published as a working paper.

0.2

OCT 2011

Specifies the message signing policies Includes test games for the test environment and the form for requesting registration for the service.

0.3

NOV 2011

Corrects errors in the support email address, which is [email protected] and other drafting errors. Publishes the form for requesting registration for the service as a separate document.

0.4

DEC 2011

Improves the response to the operation VerifyChangesRGIAJ to include the date on which the change was introduced. Attaches test game and test method for checking the functionality VerifyChangesRGIAJ.

0.5

DEC. 2nd 2011

Includes a clarification on the format of the date of birth (page 8). 8. Clarification of the non-obligatory nature of the second surname when the identification number is a NIE (page 8). 8. Clarification of the accepted format for the parameters First Name, Surname and Second Surname (pp. 8 and 9) Includes the address for downloading the public part of the DGOJ certificate (p. 11. Corrects errors in the responses to example messages in the points: 4.2.3.11 4.2.4.4 4.2.5.4 Clarification of the results of test cases in VerifyChangesRGIAJ (point 2.b, page 42)

0.6

FEB. 2012

Includes a new error type, Fault in the case of NIFs repeated in the same request. 9 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Restricts the range of characters accepted in the fields First Name, Surname and Second Surname. Changes the support email addresses. 0.7

MAR. 2012

Makes recommendations on the use of the different operations of the service, emphasising the operation VerifyChangesRGIAJ (point 2.1) Clarification on the use of input parameters to the services (point 2.2.1). Details the specifications timestamp (point 2.4.3).

for

the

message

Clarification on the signature policy regarding soap fault messages (these are unsigned) and includes examples of this type of message. Clarification of the range of characters accepted in name fields (point 2.2.1). Modifies the data of some test cases. Establishes the obligation to request the service in the production environment from specific IPs (maximum 4) 0.8

APR. 2012

Clarification with graphs of the correct use of the different web service methods (point 2.1) Clarification on the separation of string and code in soap fault messages. Includes a new functionality which enables verification of correct configuration and access to the production environment. Specifies the range of tests for this environment. (points 3.1 and 4.3)

0.9

APR. 2nd 2012

Correction of errata on the correct use of the different web service methods (point 2.1)

1.0

JUN 2012

Increased information on the correct use of the different web service methods (point 2.1 Correction of the code results and error table (point 4.1). Correction of the error message “Wrong user identity.” adding “-Holder not identified” in the cases of point 4.3, when the DNI does not exist in the test data. Specification of the 40-character length of the 10 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

fields First Name, Surname1 and Surname 2 Specification of the error to be returned if using the operation VerifyChangesRGIAJ in test mode in the production environment. Note on the IPs used to access the system in the production environment (point 3.1) 1.1

SEPT 2012

Clarification of the cases in which VerifyChangesRGIAJ takes into account the players checked (point 2.1) Details of the difference between incorrect identity check responses and the impossibility of running the check (point 4.1) Specification of a new type of error in the case COD004 (point 4.1)

1.2

FEB 2013

Clarification on valid values for date of birth (point 2.2)

1.3

MAY 2013

Establishes a new format for the URIs of the production and preproduction service in order to enable the gradual implementation of new versions of operator production environments (point 3.1) Announces the new version of the software, 2.1, involving a change to the technological environment of the DGOJ and a series of improvements, making it necessary for operators to run tests in preproduction to check the compatibility of their systems with the new technology of the DGOJ, and the functional improvements: Details the new error codes of the type COD9… (one of the functional improvements) and in the examples of test cases, updates the codes and response messages for these cases (point 4.1). Includes test cases for the operation VerifyChangesRGIAJ in the production environment until the operator can operate with real data (p. 53). Emulates the real behaviour of COD005 when working in the production environment with test cases (p. 58 and example p. 70). 11 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

1.4

JULY 2013

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Includes a new optional field (Numsupport) for identification of a NIE, solving the present problem of the D.G. of the Police detecting more than one affiliation for that NIE. Modifies the structure of “player” data in the WSDL and incorporates test games for the preproduction environment (point 2.2). Includes a new operation in the WS enabling the operator to remove a NIE/NIF. This means the operator will no longer be informed of changes to the RGIAJ status associated with the NIF/NIE from the time of requesting removal. Includes test cases for the preproduction and production environments. (point 2.1). Includes test cases in the preproduction and production environments of the operation VerifyChangesRGIAJ to check the data after removing a NIF/NIE previously reported in that operation.

1.5

October 2013

New codes and error texts of the SVDI for cases when the DNI cannot be identified –COD004­ (point 4.1). Also modifies the response messages for the examples of point 4.2 of the document, giving new response values to the texts on why the player could not be identified, and adding new examples with the new reasons. Clarification on the cases of NIEs with 10 digits (always beginning with X0 followed by 7 more digits plus the control digit), due to a previous measure by the Police (point 2.2).

1.6

DEC 2013

New functionality for checking the status of the service (section 5)

1.7

SEP 2014

Addition of length validation for names and surnames. The length must not exceed 40 characters. Introduction of a new error code, COD907, which is shown for errors in length validation.

1.8

APRIL 2015

Update of the instructions for validating the signature in responses returned by the server. 12 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Modification of the service's endpoint: previously cnjuego.gob.es, now ordenacionjuego.gob.es.

13 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

1.2 Schedule for implementing the new endpoints

PREPRODUCTION Document version

Software version

PRODUCTION

date of implementati on

date of withdrawal (1)

date of implementatio n

date of withdrawal

27/04/2015

21/10/2013

11/05/2015

1.7

2.2

23/09/2013

1.8 (2)

2.2

05/03/2015

(1)

06/04/2015

(1) After the withdrawal date no support will be provided for the environments and versions indicated. (2) This change corresponds to the endpoint change from cnjuego to ordenacionjuego. From the withdrawal date, the SSL3 protocol will cease being permitted for the establishment of connections

14 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

2 Functional specifications 2.1 Web service and operations The functional specifications of the service are defined below:

The online player verification service will have five operations: 1. “VerifyIdentity”: the operator can use this operation to check the DNI/NIE, name and date of birth of the player match the data held by the Government. This operation does not involve establishing a contractual relationship between the player and the operator, as it is assumed that the operator is making the check in the initial phase of verifying the data of residents (Article 26.3 RD. 1613/2011) during the creation of the gaming account, before it is activated. Thus any change in the player's RGIAJ status will not be reported to the operator in the service VerifyChangesRGIAJ. 2. "VerifyRGIAJ": the operator can use this operation to check whether players are registered with the RGIAJ.

15 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Although the input parameters include the full name and date of birth, the operation uses only the DNI / NIE to access the RGIAJ. When using this operation, the system assumes there is a contractual relationship between the player and the operator, as the typical use of this operation is to check that the player is not subject to an individual ban, before activating the account (art. 27.2 R.D. 1613/2011) Thus any change in the player's RGIAJ status will be reported to the operator in the service VerifyChangesRGIAJ. 3. "VerifyPlayer": the operator can use this operation to check whether players are registered with the RGIAJ and to verify their identity. This operation is intended for operators interested in running both checks at the same time due to the way they create user accounts on their gaming platforms. As they are internally independent and the RGIAJ check only requires the DNI / NIE, it is possible for a response to be produced for the RGIAJ even though the identity verification service gives a negative response or is unavailable. In this case, if the response of the RGIAJ is that the player is registered, there is no need for the operator to attempt to run the check when the identity data are corrected or the service is recovered, as the player is affected by an individual ban and cannot play. Regardless of the identity verification response, any change in the player's RGIAJ status will be reported to the operator in the service VerifyChangesRGIAJ.

4. "VerifyChangesRGIAJ": the operator can use this operation to recover players it previously checked against the RGIAJ using the “VerifyRGIAJ” or “VerifyPlayer” methods (in this case, independently of whether the identity of the player could be verified) and whose RGIAJ status has changed. This operation is not useful when any of the above operations returns a Formatting Error for the request data, so that in these cases the player is not associated with the operator. This operation facilitates the two goals stated in Article 27.2 of RD 1613/2011: a)

regular verification of the data in the operator's user accounts against the data in the General Register of Gaming Access Bans in order to prevent unauthorised gaming activity.

b)

verification that the player is not subject to an individual ban before paying out prizes (Art. 27.2 R.D.1613/2011).

It must be taken into account that in order to coordinate this function with RGIAJ entries, the entries will be activated in the hour after their inclusion in the DGOJ database. For example, all the entries added from 11:00 to 11:59 will be 16 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

registered at 12:00. “VerifyChangesRGIAJ”.

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

After

that

time

they

will

be

reported

in

Thus, it is sufficient for the operator to consult the operation “VerifyChangesRGIAJ” once an hour to obtain the list of changes in the RGIAJ concerning players who have at some time been checked for RGIAJ status (clients, who were previously accepted for user accounts due to not being registered in the RGIAJ, and who were later registered, or potential clients whose user accounts could not be created due to inclusion in the RGIAJ, and who are now no longer included). After applying this list to its database, the operator can pay out prizes excluding the clients who are registered with the RGIAJ in this list. The internal clocks of the DGOJ servers are set by an NTP server synchronised with the Royal Navy Observatory, the Spanish body responsible for maintaining and distributing the official "Coordinated Universal Time" (UTC(ROA). It is recommended that operators' servers also synchronise with the equivalent body in their respective countries. Also, it is recommended to avoid running the check VerifyChangesRGIAJ at the start of the hour, but rather at five past, in order to ensure the service has finished the publication process. 5. "removePlayer": the operator can use this operation to close the account of a player who was previously checked against the RGIAJ, using the “VerifyRGIAJ” or “VerifyPlayer” method. This means that the status of the player will not be reported in the operation VerifyChangesRGIAJ, as this operation dissolves the contractual relationship between the player and the operator. It must be taken into account that in order to coordinate this function with RGIAJ entries, which are also reported in the operation VerifyChangesRGIAJ, these removals will be confirmed in the hour after their inclusion in the DGOJ database. For example, all the entries added from 11:00 to 11:59 will be registered at 12:00. After that time they will be reported in “VerifyChangesRGIAJ”. Thus, it is still sufficient for the operator to consult the operation “VerifyChangesRGIAJ” once an hour to obtain the list of changes in the RGIAJ concerning players who have at some time been checked for RGIAJ status and whose removal has not been requested.

An explanatory diagram is given in the next figure

17 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

(1) If the operator uses the participant identification services provided by the DGOJ, this service will be used in the initial phase of the registration process to check the player's identity, and in the case of an incorrect identification, this will not continue to the next phases of the registration process where other checks are made (status in the General Register of Gaming Access Bans, RGIAJ) or additional data is requested as needed for the creation of the user account (credit cards, address, etc.). From the point of view of the DGOJ, the player and the operator are not connected. (2) To be used in the final phase of the registration process, after which, if applicable, the user account can be activated. The use of this method means that the DGOJ will associate the player with the operator making the check, so that future changes in the RGIAJ status of that player will be reported to the operator via VerifyChangesRGIAJ. (3) To be used when the registration process involves a single phase, checking the player's identity and RGIAJ status in a single step, after which, if applicable, the user account can be activated. The use of this method means that the DGOJ will associate the player with the operator making the check, so that future changes in the RGIAJ status of that player will be reported to the operator via VerifyChangesRGIAJ. It should be remembered that, apart from the exception mentioned in the above section on operations to be carried out when the services are not available, the web services 18 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

provided by the DGOJ may only be used as a result of an action initiated by the participant. 4) Given that changes in RGIAJ status take place on the hour, the data obtained by this method will be valid throughout the following hour and must be used to prevent any gaming activity in the terms of the relevant legislation. (5) Both actions must take into account the player's RGIAJ registration status. This will use the information obtained through the service VerifyChangesRGIAJ, which the operator must use to update its client database and act accordingly. (6) To be used when the operator wants to close the account of a player whose RGIAJ status was previously checked, either because they did not become a client or because they are no longer a client, and to stop receiving the reports on their RGIAJ status or changes in status. Actions to be taken if the above services are not available: 1.- Unavailability of the identity verification service (verifyIdentity or verifyPlayer service): the operator may use the alternative identity checking mechanisms available. If the operator habitually uses the identity verification services provided by the DGOJ, after the service is restored (it can make occasional checks to see if it has been restored) the identity verification services can be used to check the users who could not be verified while the system was down. 2.- Unavailability of the service verifying inclusion in the RGIAJ (methods VerifyRGIAJ and VerifyPlayer). The DGOJ will establish a contingency plan to provide this information through an alternative procedure. 3.- VerifyChangesRGIAJ: if the service is not available, another attempt will be made to download it later, and the information previously downloaded in the last check will be used. 4.- removePlayer: if the service is not available, another attempt will be made later.

2.2 Input parameters 2.2.1 VerifyPlayer, VerifyRGIAJ and VerifyIdentity In the first three operations, the input parameters of the operation are the same, although it should be noted that VerifyRGIAJ uses only the DNI/NIE, and although the full name must be specified, this will not be checked:

19 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

This is one or more occurrences of the Player type, consisting of:  DNI/NIE of the player. (obligatory) DNI/NIE is understood to mean the National Identity Document, including the identification number and the associated letter (NIF/NIE), so that the format will be one of the following: 20 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



8 digit number followed by a letter (control digit). (NIF). If the number does not have 8 digits, it will be completed with a 0 on the left.  Letter (X, Y, Z) followed by a 7 digit number and another letter (control digit), making a total of 9 characters (NIE). For the NIE an exception must be clarified, which is due to a previous measure by the Police. Before deciding that the NIE format would have 9 characters preceded by a letter (X, Y or Z), some documents were issued with 10 digits and an X at the beginning, and given the number of issues, the first digit after the X was always 0. The Web Service accepts only 9-digit NIEs, so that when a 10-digit NIE is detected, which begins with X then 0, with the total length of the NIE, including the control digit, being 10 characters, the first zero after the X must be deleted and the check made with the resulting NIE (consisting of 9 characters). Other 10-digit NIEs must be discarded, as the format is an error.  First name or names of the player, as it appears on their National Identity Document, maximum length 40 characters. (Obligatory, not checked in VerifyRGIAJ).  First (or only) surname of the player, as it appears on their National Identity Document, maximum length 40 characters. (Obligatory, not checked in VerifyRGIAJ).  First surname of the player, as it appears on their National Identity Document, with a maximum length of 40 characters. (for NIEs this field will not be mandatory. In VerifyRGIAJ it is not checked)  Birth date of player. Example: 2011-09-21. The system accepts the W3C date format, which includes the time zone, although this time zone will be discarded because it is not necessary for the service. Birth dates prior to 01/01/1900 will return an invalid format response. 

NIE support number. If the identification is done using an NIE, there will be an option to send the "Support number" associated with the Foreign National Identity Card (TIE Spanish acronym) or European Certificate to resolve cases in which the response to the WS of the D.G. of the Police is of the type “ MORE THAN ONE FILE WITH THIS IDENTIFIER HAS BEEN FOUND”. A value may only be entered in this field if the identifier is an NIE; in the case of NIF (Tax ID Number) a format error will be returned (COD906: Format error-With NIF it is not possible to send a Support number). 21 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

The format of the "Support number" should be one of the following:  The letter “E” followed by 8 numerical digits for TIEs (total mandatory length 9 positions)  The letter “C" followed by 8 numerical digits for European Certificates (total mandatory length 9 positions) Example of TIE:

The support number would be: E15459056 Example of European Certificate

22 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

The support number would be: C02161074 NOTE: As the length of the field has to be 9 positions, the numerical part is completed with zeros to the left.

Regarding the characters allowed in the name and first and second surname fields, a 23 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

series of characters that shall not be allowed in those fields, due to the fact that their use to identify persons makes no sense, shall be established. To start with the following have been established:

1234567890$&¿?¡!|()@#¬+*{}%/\

This list may be updated in later versions of the service. If the aforementioned fields contain one of these characters, error message COD902 will be returned. As shown above, those characters that may be entered by means of a conventional use of the keyboard and whose presence in names and/or surnames makes no sense have been prohibited. Therefore, the characters that can be obtained using a combination of keys (for example AltGr+’combination of keys’) would be allowed, even though their use in the someone's name/surname is illogical. Furthermore, the use of those characters would probably lead to a failure to identify the player. It should be stressed that the system is not case sensitive. Likewise, it also does not recognise vowels accented with the normal Spanish accent mark and other vowel accent marks, with the exception of the umlaut with the letter u. This can be seen in the following table:

Character received:

Character used by the system

áàäâÁÀÄÂ

A

éèëêÉÈËÊ

e

íìïîÍÌÏÎ

i

óòöôÓÒÖÔ

o

úùûÚÙÛ

U

Üü

Ü

Likewise, the system will ignore, in the aforementioned parameters, any "white space" character or dash "-" at the beginning or end of the corresponding parameter. In the case of compound names or surnames (with white spaces or dashes inside them), the system will automatically replace any two or more consecutive white spaces with one.

24 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

For technical integrity reasons, the maximum number of player verifications that can be sent in the same request has been limited to 100. If there are any repeated NIF/NIEs within a message, the entire message will be rejected with a code ERR-003 fault.

The response time for messages with various NIF/NIEs, as it does not depend on a local repository, varies and is sometimes long depending on various circumstances, all beyond the control of the DGOJ.

2.2.2 Parameters VerifyChangesRGIAJ This operation does not require input parameters because the Operator is authenticated and identified by their digital certificate. .

2.2.3 Parameters removePlayer The input parameters for this operation are a Removal-type instance consisting of:  DNI/NIE of the player. (obligatory) DNI/NIE is understood to mean the National Identity Document, including the identification number and the associated letter (NIF/NIE), so that the format will be one of the following:  8 digit number followed by a letter (control digit). (NIF). If the number does not have 8 digits, it will be completed with a 0 on the left.  Letter (X, Y, Z) followed by a 7 digit number and another letter (control digit), making a total of 9 characters (NIE). For the NIE an exception must be clarified, which is due to a previous measure by the Police. Before deciding that the NIE format would have 9 characters preceded by a letter (X, Y or Z), some documents were issued with 10 digits and an X at the beginning, and given the number of issues, the first digit after the X was always 0. The Web Service accepts only 9-digit NIEs, so that when a 10-digit NIE is detected, which begins with X then 0, with the total length of the NIE, including the control digit, being 10 characters, the first zero after the X must be deleted and the check made with the resulting NIE (consisting of 9 characters). Other 10-digit NIEs must be discarded, as the format is an error. 25 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

 Reason for Removal. (mandatory) This may contain only the following values:  'A': if the cause of the incident is an active player with the operator, who wishes to be removed  'R': if the cause is a player whose status in the RGIAJ was queried but was never activated with the operator.

2.3 Responses of the service

2.3.1 Response to VerifyPlayer

As many ResultPlayer responses will be returned as there were repetitions of the player type sent in the request. The result type contains the following information: 1. DNI verified, corresponding to the DNI/NIE sent in the request. 2. Result of verification in RGIAJ (code and description). 3. Result of verification of identity (code and description). 26 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

2.3.2 Response to VerifyRGIAJ

As many repetitions of ResultRGIAJ will be returned as there were repetition of the player type sent in the request. The result type contains the following information: 1. DNI verified, corresponding to the DNI/NIE sent in the request. 2. Result of verification in RGIAJ (code and description).

27 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

2.3.3 Response to VerifyIdentity

As many ResultIdentity responses will be returned as there were repetitions of the player type sent in the request. The result type contains the following information: 1. DNI verified, corresponding to the DNI/NIE sent in the request. 2. Result of verification of identity (code and description).

2.3.4 Response to VerifyChangesRGIAJ

The operation returns a list of DNI/NIEs, the reason for the change (“Addition” or “Removal”) and the date of the change, which corresponds to the changes to the player RGIAJ registration, which the operator would have consulted previously by means of the VerifyRGIAJ service. The ResultChangesRGIAJ type contains the following information: 1. DNI/NIE. 28 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

2. Reason for change: A-Addition, or B-Removal. 3. dateChange, date and time at which the record was changed. 2.3.5 Response to removePlayer

The operation returns a ResultRemovePlayer type occurrence. The ResultRemovePlayer type contains the following information: 1. DNI, corresponding to the ID/NIE sent in the request. 2. Result of the removal operation (code and description).

2.4 Authentication of the Operator Messages sent to the Directorate General for the Regulation of Gambling to verify players shall be signed with the digital certificate of the gaming operator, using the Web Services Security 1.0 standard (hereinafter WS-Security) to do so, according to the specifications of the framework http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuritysecext-1.0.xsd. Likewise, response messages returned by the service shall be signed with the same standard with the digital certificate of the DGOJ, except for messages corresponding to soap faults. For security reasons, the digital certificate used by the service shall not be the one used for encrypted communications through HTTPS. Operators may confirm the digital signature of the response messages by using the element found in the headers of the message. This token will correspond to the public key of the certificate used by the server for signing the message. Accordingly, the headers of SOAP response messages will be similar to the headers of the original messages; they will contain a token corresponding to the public key of the certificate used for the signature, time stamp and digital signature of the message.

29 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

An example of a request to the verification service is shown below, and it will be used to describe the elements that comprise it and which shall be necessary for the service to function correctly. Special attention must be paid to the address of the service to which the request must be sent. For the preproduction environment, accessible at the following address: 

Endpoint:https://ws-pre.ordenacionjuego.gob.es/VerificacionJugadores-2.2/VerificacionJugadores



WSDL:https://ws-pre.ordenacionjuego.gob.es/VerificacionJugadores-2.2/VerificacionJugadores?WSDL

(1)MIII9zCCB9+gAwIBAgIJALsAAAAAAAECMA0GCSqGSIb3DQEBBQUAMIHgMQswCQYDVQQG EwJFUzEu MCwGCSqGSIb3DQEJARYfYWNfY2FtZXJmaXJtYV9jY0BjYW1lcmZpcm1hLmNvbTFDMEEGA1UEBxM6 …… …. …. +Ubmq8yaWe9F/4QyOOSmO6UgDyge6fSvZawlU1QSlzt2apSEhwsUOIQKBJNq7HqJ8SVnp9Ierlty LdvOZfDckdDwjNsXneiH6lYEHA==

xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"

(2) uVmWY1Vfjnd5NxTYceLHhkmQx0Y= (3)

30 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING



ovHJ8CbnjXObbQupmJq6f++T+1A=





YYoxAiuLxhBJwPIpNgJSv+06s868zyh3Yxmzn2siMkj+r6T7Q7PixBYKsieQ

dWWSMBFBgldlc3mM

nafVJE3K9w17gFrk0e+HE/jKkEyIHxVsuuweJ/s0tAAm3+CG/k3GktiNuhZrB3WCl0XDw56ViU0O

f5x13/Qoljmg291g5Lk= (3) 2011-09-26T15:21:26Z 2011-09-26T15:21:31Z (2) 74660112L Daniel López Gómez

2100-10-02T00:00:00









31 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



Special attention must be paid to the following aspects of the request, marked in red on the example: 1. The request shall include the certificate (the public part) used to sign the request. To verify that the request corresponds to the operator registered in the system, the public part of the certificate to be used in this process must be communicated to the Directorate General for the Regulation of Gambling. To be added to the testing environment, the service registration request form indicated in Section 4.4 shall be used, and must be forwarded to the email address [email protected], writing “ADD WS-VERIFICATION” in the subject line of the message. To be added to the production environment, this information must be communicated to the Directorate General for the Regulation of Gambling during the licence granting process. The certificate code will be Base64, using the BinarySecurityToken type included in the security header of the standard. Note in the example that for the sake of clarity the content of the certificate has been abbreviated. The Operator shall be responsible for communicating any revocation of the certificate used to the DGOJ. 2. The body of the SOAP message shall be signed (tag “body”), and the signature shall be XMLDSIG, more specifically with the algorithm http://www.w3.org/2000/09/xmldsig#rsa-sha1. The reference to the body of the message is specified by means of the corresponding reference tag whose URI coincides with the identifier tag of the body of the message (wsu:Id). Soap fault messages are excluded from the signature









74660112L

Daniel

32 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

López

Gómez

2100-10-02T00:00:00









3. The timestamp of the request and the reference to it are included, including the hash: 2011-09-26T15:21:26Z 2011-09-26T15:21:31Z

ovHJ8CbnjXObbQupmJq6f++T+1A=

The elements Created and Expires must be in accordance with the dateTime type with the UTC format, as recommended by W3C (http://www.oasis­ open.org/committees/tc_home.php?wg_abbrev=wss). For security reasons only timestamps with lengths of validity of less than 300 seconds will be accepted - that is, the interval between and must be less than 300 seconds. In the interest of expediting the tests, in the preproduction environment the timestamp shall be optional, although if specified it will be validated. In the production environment, once the service is implemented, it shall be mandatory.

33 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

3 Description of the environments The services are called up by means of the URIs indicated below:

3.1 Production There may be a maximum of two versions of the service to allow operators to progressively implement one version of the service in the production systems of the client. The DGOJ will establish the calendar of the version changes with the operators, defining the endpoint and wsdl of the service with support at all times and the deadline upon which service to the old version will stop. From version 2.1 of the service, these URIs will be classified with the version number corresponding to the service, coexisting with the URIs of the previous version during a period established by the DGOJ to facilitate implementation by operators. Endpoint: https://ws.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores WSDL:https://ws.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores?WSDL

Where v is a digit that indicates the version number and r is the release number within the version. The software version corresponding to this version of the specification document (1.8) is 2.2, and therefore the URIs shall be: Endpoint: https://ws.ordenacionjuego.gob.es/VerificacionJugadores-2.2/VerificacionJugadores WSDL:https://ws.ordenacionjuego.gob.es/VerificacionJugadores-2.2/VerificacionJugadores?WSDL

This is currently the only version in service production. The numbering of the document versions does not coincide with that of the software.

For each operator, the environment shall not be enabled until a specific licence is granted, and registration in the service may not be requested until this moment by means of the form indicated in Section 4.4 34 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

However, the DGOJ may authorise production environment integration tests for operators that requested at least one specific licence in the terms contained in Section 4.3. Access to the production WS shall only be enabled for IP addresses communicated by the operators in the corresponding production environment registration form. These IPs shall be those of the servers or computers that establish communication with the DGOJ, and must therefore be individual addresses and never in numbers greater than four unless a written request is submitted. If the DGOJ decides to interrupt the service provided to an operator, the IPs communicated shall be used to prohibit traffic, and it is therefore the operator's responsibility to use unique IPs that are not shared with other operators to access the services of the DGOJ

3.2 Tests There is one single access point to the most recent version of the service. Version changes shall be announced to operators with sufficient advanced noticed, and the previous version shall be discontinued. Endpoint:https://ws-pre.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores WSDL: https://ws-pre.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores?WSDL

Where v is a digit that indicates the version number and r is the release number within the version. For this version of the document the software is version 2.2. Gaming operators that wish to perform tests with the player verification service must request registration in the testing environment using the form indicated in Section 4.4. Requests shall be sent to the email account [email protected] indicating the following in the message subject line “REGISTRATION WS-PlayerVerification”.

4 Appendices 4.1 Result and error codes The following table shows the codes that contain the types of results of the different verification operations.

35 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Result Codes Query of RGIAJ using enabled methods COD001

The user is registered with the RGIAJ

COD002

The user is not registered with the RGIAJ

COD006

The user's RGIAJ status could not be verified.

Query of identity using enabled methods COD003

The identity of the user is correct 1

The identity of the user is incorrect. Reason 1

Text clarifying the possible cause of the identification problem. As of the date of publication of this document, the following reasons exist:

COD004

1.

Unidentified holder

2.

Holder not positively identified - Nationalised Spanish Citizen

3.

The requested document may be undergoing renewal, retained, withdrawn by the courts or annulled due to duplication. For clarification, contact the Spanish Documentation Unit and Archive.

4.

More than one record with this identifier was found. This error normally appears in identification verification queries using NIEs and is due to the fact that the queried NIE has more than one affiliation in the Central Foreigner Registry. There are various reasons for changes to the affiliation since any one of the affiliation details may have been changed (name, surnames, parents' names, country of birth, nationality, date of birth, change of nationality, etc.). When a NIE-holding citizen changes any of these details (a seemingly common occurrence), the query on that particular NIE returns the above-mentioned error.

COD005

5.

DNI of the holder is annulled

6.

Document withdrawn by the courts, retained due to the existence of duplicates or annulled by the Spanish documentation unit

It was not possible to verify the identity of the user

Removal operation using enabled methods COD010

Removal correctly completed

COD021

Removal not completed, the ID is not activated for that operator.

COD022

Removal not completed, the DNI is already removed from that operator

COD023

Incorrect reason for removal

Others COD901

Incorrect data format - invalid DNI

COD902

The request contains invalid characters in *Name/surname1/surname2

36 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

*The field in which invalid characters were detected is specified.

COD903

Incorrect data format - The *Name/surname1/surname2 are mandatory*The mandatory field missing a value is specified

COD904

Incorrect data format - Birth date before 1900

COD905

Incorrect data format - Incorrect support number.

COD906

Incorrect data format ­ With NIF it is not possible to send a Support number

COD907

Length of name or surnames exceeds 40 characters

The following table shows error codes that will be displayed in the fault types of the verification operations. Error Codes ERR001

Technical error

ERR002

Invalid Gaming Operator

ERR003

The request contains duplicated player identifiers; it is not valid

Soap fault messages corresponding to this type of error will have no signature. The message code has been separated from the text since version 0.7. The latter is specified in the tag and the code in the tag within the node. It is necessary to differentiate between cases of incorrect identification of identity and cases in which it is impossible to carry out the identity identification operation. The first case pertains to requests with the results COD004, COD901, COD902, COD903 , COD904, COD905 or COD907. When any of these results are obtained, there is no sense in the operator asking for the same information again, as the answer will be the same. The information of the original request must be modified for correct identification. If even after sending different information three incorrect identification responses are obtained, the operator must abandon the attempt to identify the player using the means offered by the DGOJ, beginning a cycle of verifying the player's documents. If it is impossible to perform the identity identification operation, different actions should be taken depending on the error returned. If it is due to a failure in the DGOJ service (lack of response or when an identification request does not return the corresponding response in an estimated 30 seconds for each 37 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

individual identification request), due to a technical impossibility to resolve the request (response embodied in code COD005) or a technical error (ERR001), the operator may retry the identification after allowing the DGOJ a certain amount of time to re-establish the service (approximately 30 minutes). If duplicate players are included in the same request (ERR003), the operator may detect the problem and immediately resend the corrected request.

4.2 Trial games in the testing environment Endpoint:https://ws-pre.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores WSDL: https://ws-pre.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores?WSDL

Where v is a digit that indicates the version number and r is the release number within the version. The tests of the player verification service are based on a test registry of banned players, with simulated data, the content of which is controlled by the DGOJ and the Identity Information Verification Service (SVDI) offered by the Secretary of State for Public Administrations, the content of which can vary over the test period due to the needs of the SEAP itself or of other users of the system. Therefore the objective of the tests is to verify the connectivity of the operator's system with the service, its authentication mechanisms, the secure traffic of messages and the use of exchanged messages, not so much the content of the information and the answers given by the service. Likewise, stress tests of the testing environment with a large volume of information must not be undertaken without notifying the DGOJ beforehand. Technical incidents or questions should [email protected] with

be

sent

to

the

email

address

“TESTS WS-PlayerVerification” in the subject line of the message.

4.2.1 Description of the test cases

This section contains a list of the test cases for the verifyPlayer, verifyIdentity, verifyChangesRGIAJ and the removePlayer operations of the online player verification service (PlayerVerification) that the DGOJ shall offer the different gaming operators 38 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

WSDL: PlayerVerification.wsdl. NOTE: The system is not case sensitive, and does not recognise accented vowels used in Spanish or any other vowel. Likewise, it also does not recognise vowels accented with the normal Spanish accent mark and other vowel accent marks, with the exception of the umlaut with the letter u. Likewise, note how white spaces are processed (pp. 8 and 9) Operation: verifyPlayer The SOAP message is not specified in its entirety for each test case - only the information of the node for the Request message and the information of the node for the Response message. Request (players):



Parameter: DNI (string): DNI/NIE of the player.



Parameter: name (string) : Name of Player



Parameter: surname1 (string) : First surname of player



Parameter: surname2 (string) : Second surname of player



Parameter: dateBirth (date) : Date of birth of the player



Parameter: supportNum (string) : NIE support number.

Response (resultPlayer):



Value for DNI (String) : DNI/NIE of the player.



resultRGIAJ: o code: (string) : return code o description (string): description of the return code



resultIdentity: o code: (string) : return code o description (string): description of the return code

Therefore the following information is specified for each test case: Request: 10000320N

39 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

MARIA ENCINA FELIZ VARELA 1944-05-18

Response: 10000320N COD001 El usuario está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

Operation: verifyIdentity The SOAP message is not specified in its entirety for each test case - only the information of the node for the Request message and the information of the node for the Response message. Request (jugadores):



Parameter: DNI (string): DNI/NIE of the player.



Parameter: name (string) : Name of Player



Parameter: surname1 (string) : First surname of player



Parameter: surname2 (string) : Second surname of player



Parameter: dateBirth (date) : Date of birth of the player



Parameter: supportNum (string) : NIE support number.

Response (resultIdentity):



Value for DNI (String) : DNI/NIE of the player. 40 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS



DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

resultIdentity: o code: (string) : return code o description (string): description of the return code

Therefore the following information is specified for each test case: Request:

10000320N

MARIA ENCINA

FELIZ

VARELA

1944-05-18





Response: 10000320N COD003 La identidad del usuario es correcta

Operation: verifyRGIAJ The SOAP message is not specified in its entirety for each test case - only the information of the node for the Request message and the information of the node for the Response message. Request (jugadores):



Parameter: DNI (string): DNI/NIE of the player.



Parameter: name (string) : Name of Player



Parameter: surname1 (string) : First surname of player

41 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



Parameter: surname2 (string) : Second surname of player



Parameter: dateBirth (date) : Date of birth of the player



Parameter: supportNum (string) : NIE support number.

Response (resultsRGIAJ):



Value for DNI (String) : DNI/NIE of the player.



resultRGIAJ: o code: (string) : return code o description (string): description of the return code

Therefore the following information is specified for each test case: Request: 10000320N MARIA ENCINA FELIZ VARELA 1944-05-18

Response: 10000320N COD001 El usuario está inscrito en el RGIAJ Formato de datos incorrecto - Baja no realizada, causa de la baja errónea

4.2.7.5 Removing a player sending an incorrect DNI/NIE This test case involves requesting the removal of a player that is incorrectly identified due to the fact that an incorrect DNI/NIE letter was sent (the correct DNI/NIE is 30000260A). Therefore the removal is not completed, and this information is given in the request result. Request:

30000260B

A

83 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



Response:

30000260B



COD901 Formato de datos incorrecto - DNI no válido

4.2.7.6 Removing a player without sending a DNI/NIE In this test case, the removal of a player is requested but the mandatory DNI/NIE is not sent. Therefore the removal is not carried out, and this is reported through the services' fault. Request:

A



Response: soap:Client Unmarshalling Error: cvc-complex-type.2.4.a: Invalid content was found starting with element 'causa'. One of '{dni}' is expected.





4.2.7.7 Removing a player without sending the reason In this test case, the removal of a player is requested without sending the reason, 84 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

which is mandatory. Therefore the removal is not carried out, and this is reported through the services' fault. Request:

10000949C



Response: soap:Client Unmarshalling Error: cvc-complex-type.2.4.b: The 'bajaJugador' is not complete. One of '{causa}' is expected.

content

of

element



4.2.7.8 Verify changes in the RGIAJ after a removal In this test case, one of the DNIs indicated in the VerifyChangesRGIAJ test case and that has been previously verified through the verifyPlayer or verifyRGIAJ is removed. After the following hour on the hour, upon calling the verifyChangesRGIAJ operation, it will be confirmed that the DNI nor longer appears in the list in the response.

Example: Beforehand, both DNI 00000058N and DNI 31313131B were verified, and by calling the verifyChangesRGIAJ operation, it was confirmed that both appear in the list.

Response: 00000058N A 2011-11-01T14:07:13.257+01:00

85 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



31313131B

B

01/11/2011T17:01:05.257+01:00



In this test case, DNI 00000058N is removed using the removePlayers operation, and then the VerifyChangesRGIAJ is called again, after waiting until the next hour on the hour. This DNI no longer appears in the list of results.

Response:

31313131B

B

01/11/2011T17:01:05.257+01:00



86 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

4.3 Trial games to verify the production environment Endpoint: https://ws.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores WSDL:https://ws.ordenacionjuego.gob.es/VerificacionJugadores-v.r/VerificacionJugadores?WSDL

Where v is a digit that indicates the version number and r is the release number within the version. At the request of the operators that have requested a specific licence and once the tests performed in the preproduction environment have been analysed, the DGOJ can authorise the performance of tests for integration in the production environment, without using real data, using the trial game described in this section. This production test environment includes all the operations available in the production environment for real cases. Companies must have previously requested registration in the production environment under the conditions indicated in Section 4.4. Once access is granted, companies must report the beginning and end of these tests to the email address [email protected] indicating “TEST WS-VerificationPlayers” in the subject line. The DGOJ will authorise the start and end dates and times of the tests in the production environment once they have verified that the company has requested the specific licence and that the preproduction environment tests were satisfactory.

4.3.1 List of generic error cases

4.3.1.1 Blank mandatory data fields If any of the information established as mandatory in the service is blank, a framework error is returned to the service's soapfault.

4.3.1.2 Authentication of the Operator If the Operator is not correctly authenticated, a message will be returned indicating that the Operator is invalid in the service's soapfault.

4.3.1.3 Validation of DNI/NIE format If the format of the DNI or NIE is not correct, the code “COD901- Incorrect data format 87 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

–Invalid DNI” will be returned for all results for that player.

4.3.1.4 Validation of the DNI/NIE letter If the letter of the DNI or NIE is not correct, the code “COD901- Incorrect data format –Invalid DNI” will be returned for all results for that player.

4.3.1.5 Validation of Surname2, mandatory for an NIF If an NIF is queried and the second surname is blank, the code “COD903­ Incorrect data format – *Name/Surname1/Surname2 is mandatory” will be returned (specifying which mandatory field is blank) for all results for that player. 4.3.1.6 Validation of date of birth after 01/01/1900 If a date of birth prior to 01/01/1900 is queried, the code “COD904­ Incorrect data format – Date of birth prior to 1900” will be returned for all results for that player.

4.3.1.7 Validation of invalid characters If the name or surnames contain any of the characters considered invalid (such as, for example, numbers, $, %, etc.) the code “COD902-The request contains invalid characters in *Name/Surname1/Surname2” is returned (specifying which field contains the invalid characters) for all player results with incorrect information" for all player results. 4.3.1.8 Repeated DNI or NIE If a batch of players is sent in which one of the DNIs or NIEs is repeated, a message will be returned indicating that the request has duplicate player identifiers in the soapfault of the service. COD005 In order to emulate the possible behaviour of the WS in the production environment accessing real data, returning COD005 during a certain amount of time, and then recovering the service, in the test cases in the production environment, when the result of VerifyIdentity is COD005, after the third query attempt COD003 will be returned. Validation of the support number format If the support number is not correctly formatted, the code “COD905- Incorrect data format - Incorrect support number, ” will be returned for all results for that player.

88 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

Validation of support number with NIF If an NIF is sent with a support number, the code “COD906 - Incorrect data format ­ A support number may not be sent with NIF” will be returned for all results for that player.

4.3.2 Test Cases for the verifyPlayer operation 4.3.2.1 Verify a player NOT OK-NOT IN RGIAJ In this test case, the player is incorrectly identified and is not registered in the RGIAJ. Therefore the Operator should not allow them to be added because they are incorrectly identified. Request:



00000000T

MARIA

GONZALEZ

LOPEZ

1960-04-10



Response:

00000000T

COD002

El usuario no está inscrito en el RGIAJ COD004 La identidad del usuario es incorrecta - TITULAR NO IDENTIFICADO

89 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



4.3.2.2 Verify a player OK- IN RGIAJ In this test case the player is correctly identified and is registered in the RGIAJ. Therefore the Operator should not allow them to be added because they are registered in the RGIAJ. Request:



00000034B

EMILIO JOSE

GARCIA-RUIZ

GONZALEZ

1953-08-01



Response:

00000034B COD001 El usuario está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

90 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

4.3.2.3 Verify two players OK- NOT IN RGIAJ In this test case, two players are sent, both are correctly identified and neither are registered in the RGIAJ. Therefore they may be added by the Operator.

Request:



00000060Z

Santiago

Martín

Güel

1982-02-23





X0000040V

Pedro

Araña



1977-09-09



Response:

00000060Z COD002 El usuario no está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

91 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

X0000040V COD002 El usuario no está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

4.3.2.4 Verify two players, one OK- NOT IN RGIAJ and another with FORMAT ERROR In this test case, two players are sent. The first player is correctly identified and is not registered in the RGIAJ, and therefore may be added by the Gaming Operator. The second player is not correctly identified since the letter of the DNI was incorrect (the correct DNI is 00000018H). Therefore the Operator should not allow them to be added because they are not identified. Request:

Y9999999G Esperanza San Juan Mateo 1985-06-05 00000018K Carlos Guerrero

92 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Grau 1996-05-11

Response:

Y9999999G COD002 El usuario no está inscrito en el RGIAJ COD003 La identidad del usuario es correcta 00000018K COD901 Formato de datos incorrecto– DNI no válido COD901 Formato de datos incorrecto – DNI no válido

4.3.2.5 Verify two players, both OK- IN RGIAJ In this test case, two players are sent. Both are correctly identified and are registered in the RGIAJ. Therefore the Operator should not allow them to be added because they are registered in the RGIAJ.

93 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

Request:



00000024R

Juan Manuel

Terras

Colon 1962-09-20 00000057B Maria Fernanda Velas Leon 1973-04-06

Response:

00000024R COD001 El usuario está inscrito en el RGIAJ COD003 La identidad del usuario es correcta 00000057B COD001 El usuario está inscrito en el RGIAJ

94 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

COD003 La identidad del usuario es correcta

4.3.2.6 Verify a player OK- NOT IN RGIAJ In this test case, a correctly identified player not registered in the RGIAJ is sent. Therefore they may be added by the Operator. Request:

X0000066C Susana Ayala Gracia 1971-09-24

Response:

X0000066C COD002 El usuario no está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

95 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING



4.3.2.7 Verify a player NOT OK- IN RGIAJ In this test case, a correctly identified player not registered in the RGIAJ is sent. Therefore they may be added by the Operator. Request:

X0000019L Hassan Almud 1960-01-01

Response:

X0000019L COD001 El usuario está inscrito en el RGIAJ COD004 La identidad del usuario es incorrecta - TITULAR NO IDENTIFICADO POSITIVAMENTE - CIUDADANO NACIONALIZADO ESPAÑOL

96 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

4.3.2.8 Verify a player OK- NOT IN RGIAJ (but a minor) In this test case, the player is correctly identified and is not registered in the RGIAJ. However, the player is not of legal age and therefore the Gambling Operator should not allow them to be added.

Request:



00000018H

Carlos

Guerrero

Grau

1996-05-11





Response:

00000018H COD002 El usuario no está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

4.3.2.9 Verify a player missing mandatory information In this test case, the name was not sent (it should have been “LORENA). Therefore the Gaming Operator must not allow them to be added. 97 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

If the name is sent, the identification is correct and they are registered in RGIAJ. Request:



00000001R

D´con

Fernandez Ruiz

1955-05-18



Response:

Error de Esquema en el soapfault del servicio: env:Server org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'apellido1'. One of '{nombre}' is expected.

4.3.2.10

Verify a player OK- IN RGIAJ

In this test case the player is correctly identified and is registered in the RGIAJ. Therefore the Operator should not allow them to be added because they are registered in the RGIAJ. Request:

X0000052Y OSCAR L•ÜÇÄR

98 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC ADMINISTRATIONS

DIRECTORATE GENERAL FOR THE REGULATION OF GAMBLING

1964-03-03

Response:

X0000052Y COD001 El usuario está inscrito en el RGIAJ COD003 La identidad del usuario es correcta

99 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

4.3.2.11

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

Verify a player without sending a date of birth

In this test case, a player is sent without their date of birth (which is “1992-08-20”). Therefore, the Operator should not allow them to be added as they are not correctly identified. If the date is sent, it will return that the player is not identified and not registered in the RGIAJ,

Request:



00000047R

XAVIER

Cañas

Gonzalez



Response:

Error de Esquema en el soapfault del servicio env:Server org.xml.sax.SAXException: cvc-complex-type.2.4.b: The content of element

'jugadores' is not complete. One of '{nombre}' is

expected.





100 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

4.3.2.12

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

Verify a player for which NO DNI EXISTS

In this test case, a player who is not among the test DNIs is sent, and therefore the service returns that they are not identified or in the RGIAJ. Therefore, the Operator should not allow them to be added because they are not identified. Request:

00000074M MARIA GARCIA PEREZ 1990-09-01/fechaNacimiento>

Response:

00000074M COD002 El usuario no está inscrito en el RGIAJ COD004 La identidad del usuario es incorrecta - TITULAR NO IDENTIFICADO

101 of 132

CAPITÁN HAYA, 53 – 6th floor 28071 - MADRID TEL. +34 91 596 26 14 FAX +34 91 596 24 56

STATE SECRETARIAT FOR FINANCE

MINISTRY OF FINANCE AND PUBLIC

ADMINISTRATIONS

4.3.2.13

DIRECTORATE GENERAL FOR THE

REGULATION OF GAMBLING

Verify a player that returns a Service error (COD005)

In this test case, a player is sent for which the response will be that the identity of the user could not be identified (COD005). This response is obtained the first two times a request with this DNI is made in one day. After the third request with this DNI on the same day, the service will return that a correct identification was possible (COD003), to simulate a behaviour that will occur with real data.

Request:

00000015S JAIME TOLEDO HERNANDEZ 1992-08-17

Response:

The first two requests in one day:

00000015S COD002 El usuario no está inscrito en el RGIAJ COD005

Get in touch

Social

© Copyright 2013 - 2024 MYDOKUMENT.COM - All rights reserved.