APIs
Sub-processorsAbout PismoContact us

Confirmation of payee [beta]

post
https://sandbox.pismolabs.io/fps/v1/payments/fps/cop

Verify a beneficiary's account name before making an FPS payment using the Confirmation of Payee (CoP) service.

CoP allows payers to check that the name they have for the intended recipient matches the actual name on the recipient's account, reducing the risk of fraud and misdirected payments.

This verification does not create an FPS payment transaction. The request is forwarded to the payment provider for real-time name verification.

This endpoint generates a CoP name verification requested event. The result is received in a CoP name verification result received event.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

COP verification request body

uuid
required
length ≤ 36

UUID identifier for this COP verification request.

string
enum
required

Account classification type.

Allowed:
string
required
length between 8 and 8

BBAN account number (exactly 8 numeric characters).

string
enum
required

Account number format code.

  • BBAN - Basic Bank Account Number. Currently the only supported format.
Allowed:
string
required
length between 6 and 6

Bank identifier - sort code (exactly 6 numeric characters).

string
enum
required

Bank identifier code type.

  • GBDSC - Great Britain Domestic Sort Code. Currently the only supported format.
Allowed:
string
required
length ≤ 135

Account name to verify.

string
length ≤ 35

Secondary reference to identify the account, such as a roll number for building society accounts. A building society roll number is a unique alphanumeric identifier — often 10-12 digits or a mix of letters and numbers — used to identify specific savings or mortgage accounts.

Headers
string
required

Account token - token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a 401 Unauthorized message

string
required

Organization identifier.

string
required

A UUID to ensure the operation remains idempotent, allowing for operation repetition without causing unintended effects or duplication. An idempotent operation is one that can be applied multiple times, yet the outcome remains the same. it ensures that network errors, retries, or failures can occur without introducing inconsistencies.

string

Request tracking identifier. If not provided, a random UUID will be generated.

Responses

Updated 11 days ago

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 11 days ago