Reference - Agentic Banking Documentation

The SurePay integration verifies payee details before a payment completes, so account holders can confirm they are paying the intended beneficiary through the SurePay Verification of Payee (VoP) service. For the environment details you send to Backbase, see Get started.

Supported operations

The SurePay connector supports the following operation.

Verify payment beneficiary details

Ensure that the beneficiary details provided by the end user (or saved in their contact for VoP only) are accurate before completing a payment.

Events

This connector is synchronous and doesn’t publish or consume events.

Error mapping

For the full list of Banking OS error codes and their descriptions, see Error codes. The following table maps each SurePay VoP error code to its Banking OS counterpart:

SurePay VoP code	Banking OS code
`CLIENT_INVALID`	`GC002`
`CERTIFICATE ITEMS`	`GC025`
`CLIENT_INCONSISTENT`	`GC025`
`DUPLICATED_FIELD`	`GC025`
`INVALID_FIELD`	`GC025`
`INVALID_HEADER`	`GC025`
`INVALID_REQUEST`	`GC025`
`MANDATORY_HEADER_NOT_PROVIDED`	`GC025`
`MANDATORY_FIELD_NOT_PROVIDED`	`GC025`
`MUTUALLY_EXCLUSIVE_FIELDS_USED`	`GC025`
`NAME_TOO_LONG`	`GC025`
`TIMESTAMP_INVALID`	`GC025`
`INTERNAL SERVER ERROR`	`GC027`

The following table maps each SurePay CoP error code to its Banking OS counterpart:

SurePay CoP code	Banking OS code
`NO_VALID_TOKEN`	`GC002`
`UNAUTHORIZED_CLIENT`	`GC002`
`INVALID_VALUE`	`GC024`
`INVALID_COP_RESPONSE`	`GC025`
`MISSING_VALUE`	`GC025`
`GENERIC_ERROR`	`GC027`
`INTERNAL_SERVER_ERROR`	`GC027`
`TIMEOUT`	`GC063`