Skip to main content

Verify a bank signing target

POST 
/v1/onboarding-cases/:case_id/signing-targets/:target_id/verify

Proves that the registered reference points at the key you described. The platform resolves backend_ref at the key provider, retrieves the public key, and checks that the algorithm, the public key and its SHA-256 fingerprint match what you registered. Verification does not sign anything on the network and does not activate the key; keys become active only when onboarding is activated. No request body is sent.

Required scope: connector:onboarding:artifacts:write.

Allowed states: AWAITING_BANK_ADMIN, BANK_CONFIGURING, NEEDS_CHANGES. In any other state the verification result cannot be recorded and the call returns 404.

Outcomes:

  • Match: the target becomes VERIFIED, verified_at is set, verification_error is cleared, and the call returns 200.
  • Mismatch, unknown key or access denied: the target is recorded as FAILED with the reason in verification_error, and the call returns 422 with the same reason in detail.
  • The key provider or the platform is temporarily unreachable: the target is left unchanged and the call returns 503. Retry later.

You can call verify again at any time while the case is editable, for example after fixing the key policy; a later success replaces a FAILED state.

Request​

Responses​

The target is now VERIFIED.