Initiating a CoP lookup

ℹ️

To make use of this function, please contact your Zepto Account Manager and enable the cop_account_validations scope within your Zepto API settings.

Parameters

When initiating an alias lookup, you’ll need to specify the following request parameters:

Parameters

Description

account_identifier: type* (required)

bban

account_identifier: value* (required)

The BSB and Account Number (e.g. 1234560987654321)

party_name* (required)

The party name to validate against the account.

requester: id* (required)

A unique identifier of the end customer.

Requester Information

The requester object (i.e. id) is used as a way of enforcing enumeration controls based on the end-user requesting this CoP lookup. This is done as an integral component of Zepto's strategy for preventing fraudulent activities and safeguarding against enumeration attacks, ultimately ensuring the security of the end customer's data. Zepto will be able to provide further details around fraud prevention and usage limits during technical discussions.


Endpoint

POST /cop/account/validate

Request Payload

{
  "account_identifier": {
    "type": "bban",
    "value": "06200011111111"
  },
  "party_name": "Murray Watego",
  "requester": {
    "id": "user1234abcd"
  }
}

Response

Upon submission, a response will show one of the following:

  • Successful: 200 response with match outcome
  • Failed: 422 Unprocessable entity with corresponding error message

Notable Fields

Value

Description

result

Match result:

  • match
  • close_match
  • no_match
  • account_closed

match_name

The name matched from the Data Holder.

insights: risk_score

A proprietary risk score from 0 to 100, where 100 indicates the highest risk.

(Alpha - Additional information coming soon)

insights:is_joint

True or False

insights:suggested_payment_channels

npp.sct or de.dc