Online Data Provisioning API Specification

The SurePay Confirmation of Payee (CoP) solution requires account data to be provisioned by the bank for which the CoP request is processed, and for which the input name is matched against the account name. The data therefore consists of all known attributes of the account and of the account holder(s) that are relevant for the matching algorithm. The source within the bank is usually one or multiple CRM systems and alike, and the data includes amongst others the first name and last name in case of a personal account or the legal name and trade names in case of a business account.

The actual data is provisioned either via online provisioning or offline batch-oriented provisioning. In the case of online provisioning, the bank will need to provide a real-time and highly available service for retrieving account data per specific sort code and account number. In the case of batch-oriented provisioning, the bank will need to provide bulk data files on a daily basis that are stored by SurePay in a local datastore for fast retrieval. On this page you can find the document that describes the technical specification of online account data provisioning to SurePay.

Based on this specification, the provider of the data should be able to expose a Restful API over HTTP and allow the SurePay solution to access it with required security and performance levels. In addition to this document the API specification can be downloaded as a Swagger/OpenAPI file.