Unlike Option 1, clients will need to present a landing page to their PSU and display this on redirection from Token. The client will need to take the PSU on a ‘standard’ login journey which is familiar to the PSU. Once the client has validated their PSU (login credentials plus a second factor) they will exchange details with Contis in order that Contis can store consent and be able to respond to PSU/TPP requests, see client integration
Development
- Quick Start Guide
- Environments
- Setup SFTP
- API Connectivity
- Encryption
- Workflows
- Business Signup
- Webhooks
- Card status
- Account status
- Account balance change
- HOSC
- KYC check
- Grey list check
- Transaction
- Direct debit rejection
- Authorisation
- User status change
- Token OTP
- Token activation
- Transaction & available balance
- 3DS SCA HTTP Post
- User login block/unblock
- Contact update
- OTP for SDK
- OTP for Verifying PSU with SCA
- Card Shipment
- Cross border payment regulation 2
- Bank File
- Pending authorisation auto release notification
- Buffer Account
- Open Banking
- Request to Pay (Ordo)
- Strong Customer Authentication
- SEPA
- International Payments
- Faster Payments
- W2Global Data eKYC
- Data Protection Guidelines
- PCI DSS Guidelines