Developer Portal
    • API Catalogue
    • Confirmation of Payee (CoP) Requester
      • API Specifications
        POST
    • Confirmation of Payee (CoP) Responder
      • API Specifications
        POST
    • Requester – Payee Verification (JSON)
      • API Specifications
        POST
    • Requester – Payee Verification (XML)
      • API Specifications
        POST
    • Responder - Combined Lookup
      • API Specifications
        POST
    • IBAN Validation
      • API Specifications
        POST
    • Requester Batch Check Payee
      • API Specifications
        POST
    • Responder Accounts Upload
      • API Specifications
        POST
    • Schemas
      • 400
      • 401
      • ErrorData
      • ErrorResponse
      • NameVerificationRequest
      • NameVerificationRequestData
      • ResponseData
      • Response
      • VerificationReport
      • SuccessResponse
      • NameVerificationData
      • NameVerification
      • BankCustomerResponse
      • ResponseMessage
      • BankAccountValidationRequest
      • BankAccountValidationRequestData
      • BankAccountValidationResponse
      • TransformedResponse
      • AccountId
      • CreditTransferTransactionInformation
      • Creditor
      • CreditorAccount
      • CreditorAgent
      • CreditorIdentification
      • CustomerCreditTransferInitiation
      • Debtor
      • DebtorAgent
      • FinancialInstitutionId
      • GroupHeader
      • OrganisationId
      • OtherIdentification
      • PainValidationDataDto
      • PaymentInformation
      • RemittanceInformation
      • SchemeName
      • CustomerPaymentErrorStatusReport
      • CustomerPaymentStatusReport
      • ErrorReason
      • Reason
      • InfoBlock
      • Envelope
      • ErrorStatusReasonInformation
      • StatusReasonInformation
      • SupplementaryInformation
      • TransactionInfoAndErrorStatus
      • TransactionInfoAndStatus
      • VopResponseDto
      • LookupRequestData
      • LookupRequest
      • LookupResponse
      • IBANResult
      • BadRequestResponse
      • BadRequestDetail
      • UnauthorizedResponse
      • UnauthorizedDetail
      • ForbiddenResponse
      • ForbiddenDetail
      • NotFoundResponse
      • NotFoundDetail
      • MethodNotAllowedResponse
      • MethodNotAllowedDetail
      • InternalServerErrorResponse
      • InternalServerErrorDetail
      • ServiceUnavailableResponse
      • ServiceUnavailableDetail

    Confirmation of Payee (CoP) Responder

    Overview
    Quick Start Guide

    Account Lookup API#

    TechnoXander is pleased to offer its Account Lookup API to Payment Service Providers (PSPs) looking to respond to Name Verification requests during the payment process.
    The Account Lookup API allows PSPs to send requests containing minimal identifiers such as Account Type, Account Number, Sort Code, Name, and Secondary Identification. The API checks this against available customer records and returns a list of potential matching accounts if found.
    The API is designed to be compliant with relevant privacy and data security standards.
    By designing solutions around this API, PSPs can gain access to Confirmation of Payee functionality without having to integrate directly with each bank. The API abstracts the underlying routing logic, allowing developers to focus only on calling endpoints and processing responses. Transactions are digitally signed for security, ensuring that sensitive financial data is never stored and remains under the owner's control.
    TechnoXander is fully prepared to integrate with all CoP-enabled PSPs, offering a seamless and fully compliant payment verification service. Interested parties are invited to review the technical specifications and register for CoP access.
    The API specifications comply fully with Pay.UK requirements for the submission of Confirmation of Payee requests. This establishes a common standard for request submissions and response receipts across PSPs of all sizes.

    To support the needs of different Responder PSPs to enable querying against the Customer Account information, TechnoXander provides 4 integration options:
    Core Banking Integration
    Database Integration
    Secure File Transfer
    File Upload via Responder Portal
    Each integration option is explained in detail below.

    A. Core Banking Integration#

    Simplify account lookups across your core banking systems using the Account Lookup API.

    Key Benefits#

    Unified search across accounts through a single endpoint
    Standardised response format hides the complexity of underlying systems
    Near real-time results by aggregating multiple backend queries
    Handles authentication, authorisation when calling core banking APIs
    Scalable architecture that minimises the load on core banking infrastructure
    Can be customised to work with all major Core Banking Systems
    Quick implementation Timeframe of 1 week

    How It Works#

    When the Requester PSP initiates a Name Verification Request, the TechnoXander CoP Responder module in turn initiates an Account Lookup API Request with the Responder PSPs Core Banking systems (e.g. Temenos T24, BaNCS, Oracle Flexqube, Finacle, etc.) simultaneously. It then standardises and returns the aggregated response to the CoP Responder Module while maintaining high performance.
    Account_Lookup_API_Core_Banking-fe9535a8.png

    B. Database Integration#

    Easily search and retrieve customer account data from your backend database through a centralised integration API.

    Key Benefits#

    Unified search and filtering across all account types
    Standardised response format abstracts database schema
    Near real-time results by directly querying the accounts database
    Handles authentication, authorisation for database access
    Scalable architecture to minimise load on database servers
    Can be customised to work with all major Databases
    Quick implementation Timeframe of 1 week

    How It Works#

    When the Requester PSP initiates a Name Verification Request, the TechnoXander CoP Responder module in turn initiates an Account Lookup API Request query with the Responder PSPs Accounts Database (e.g. MySQL, PostgreSQL, MongoDB, Oracle, etc.) simultaneously. It then standardises and returns the aggregated response to the CoP Responder Module while maintaining high performance.
    Account_Lookup_API_Accounts_Database-1b353f79.png

    C. Secure File Transfer#

    Quickly search and retrieve customer account data through a simple API integrated with your secure CSV files.

    Key Benefits#

    Search accounts by Customer Identifier, Name, Account Number and Sort Code
    Results return instantly from parsed CSV files
    Standardised JSON response for easy consumption
    Handles authentication and authorisation
    Quick implementation Timeframe of 24 hours

    How It Works#

    When the Requester PSP initiates a Name Verification Request, the TechnoXander CoP Responder module in turn initiates an Account Lookup API Request query with the Responder PSPs CSV file stored in a Secure server. It then standardises and returns the aggregated response in JSON to the CoP Responder Module while maintaining high performance.
    Account_Lookup_API_SFTP-7ba7ce3b.png

    D. File upload in Responder Portal#

    Quickly search and retrieve customer account data from TechnoXander backend where the Responder PSP has previously uploaded the Customer Account data through the Responder Portal.

    Key Benefits#

    Unified search and filtering across all account types
    Standardised response format
    Near real-time results
    Handles authentication and authorisation
    Quick implementation Timeframe of 24 hours

    How It Works#

    When the Requester PSP initiates a Name Verification Request, the TechnoXander CoP Responder module in turn initiates an Account Lookup API Request to the TechnoXander Backend where the Responder PSP has previously uploaded the Customer Account data through the Responder Portal. It then standardises and returns the aggregated response to the CoP Responder Module while maintaining high performance.
    Account_Lookup_API_File_upload-7f0f39e2.png
    Previous
    API Specifications
    Next
    API Specifications
    Built with