An update of the interface specifications will be published in December to align with the EPC VoP Official field definitions coming from ISO 20022.
This API based service is provided to responding PSPs participating in the Worldline VoP Hub ecosystem. It allows responding PSPs to manage account holder identification data via the Worldline VoP Hub. It allows the Hub to use this locally stored data to provide answers to requesting PSPs, verifying the identity of payee for their payer user (Requester).
The data of the responding PSP is maintained and secured by Worldline on a mutualized infrastructure in the public cloud. Logical segregation and at rest data encryption is in place.
Features
The service, offers a CRUD real time interface to manage account holder identification data for the responding PSP.
The API supports storing multiple names, as well as additional identifiers when supported by the responding bank.
File based account data management
For clients wanting to avoid API integration, Worldline can put in place file based daily upload and updates of account holder identification data via CSV or JSON formats (see API format for bulk creation), transferred via dedicated SFTP channels, and via manual upload in our Backoffice in the future.
API Security
- Authentication: The Worldline VoP Hub uses an authentication service that adheres to the OIDC standard protocol.
For enhanced security, the client must present a (qualified) SSL certificate to authenticate. - Secure Communication: All communications utilize MTLS with TLS 1.2 or higher, ensuring that data in transit is secure.
To learn more about how security at the transport layer is implemented through encryption, token management, and digital signatures to protect communication and authentication processes, please visit our Security pages.