09. Sandbox Test Accounts and Test Data

• General information
  
• PSU-ID credentials
• PSU accounts
• PSU transactions and standing orders
• Challenge
  • Example 1 - authenticationType = SMS_OTP
  • Example 2 - authenticationType = CHIP_OTP
• How to trigger decoupled SCA

General information

XS2A Sandbox has predefined test data that can be used for test purposes:

• PSU-IDs
• PSU passwords
• accounts
• balances
• transactions

You are not allowed to create your own test data besides consents and payments.

Important: in XS2A, Sandbox-created payments don't have an impact on balances and transactions. It means that an authorised payment will not be listed as a transaction on the accounts that were used as debtor and creditor accounts in the payment.

PSU-ID credentials

{
"tppMessages": [
{
"category": "ERROR",
"code": "BANK_NOT_IMPLEMENTED",
"text": "The request can't be completed, the functionality is not implemented on ASPSP side."
}
]
}

PSU accounts

PSU transactions and standing orders

Transactions and standing orders are available for all test PSUs, except aspsp1.

Challenge

Example 1 - authenticationType = SMS_OTP

current time = 17:08

• challenge data = "1507" is valid
• challenge data = "1608" is valid
• challenge data = "1909" is valid

Example 2 - authenticationType = CHIP_OTP

current date and time = 21.01.2019 17:08

• challenge data = 2107 is valid
• challenge data = 2208 is valid
• challenge data = 2009 is NOT valid

How to trigger decoupled SCA

To trigger Decoupled SCA please use authenticationMethodId where "authenticationType" =  "PUSH_OTP” in the response in the Step 3 “Provide PSU password”.

Other authenticationTypes trigger Embedded SCA.

Example response in Step 3

Example

{
"scaStatus": "psuAuthenticated",
"scaMethods": [
{
"authenticationType": "SMS_OTP",
"authenticationMethodId": "sms"
},
{
"authenticationType": "CHIP_OTP",
"authenticationMethodId": "chip"
},
{
"authenticationType": "PUSH_OTP",
"authenticationMethodId": "push"
}
],
"_links": {"selectAuthenticationMethod": "/v1/transaction-history-authorisation/{authorisationId}"}
}

Example request in Step 4 “Provide 2^nd factor”

Example

{
"authenticationMethodId": "push"
}

This request will trigger decoupled SCA logic in the XS2A-server and the bank-mock on the Sandbox.

On default, each decoupled SCA is completed successfully.

To verify the status of the SCA in decoupled case, TPP has to execute additional call to get payment or consent status, or respective authorization status.