Submit KYC evidence
PUT/users/:id/kyc
Machine token. Called by your backend, using your client_credentials token.
Records the identity evidence you hold for this customer. Evidence only — the record always becomes PENDING, and sending a status field is refused with 403. GoHubPay is the e-money issuer, so the verification decision is ours: it is made on POST /users/{id}/kyc/decision, which tenants cannot call. Re-submitting evidence returns an already-VERIFIED record to PENDING, because a decision made against different documents no longer holds.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 500
OK
Malformed request — validation failure, or a header such as Idempotency-Key is missing or not a UUID.
Missing, expired, or untrusted bearer token.
Authenticated but not permitted — the caller's role or scope does not grant this operation, or the resource belongs to another tenant.
The referenced wallet, transaction, user, or tenant does not exist within the caller's tenant.
Idempotency conflict — a request with this Idempotency-Key is still in flight. Retry once it settles. A key belonging to an already-completed request is NOT an error: the original response is replayed with its original status.
The request is well-formed but violates a business rule — for example a posting that would breach a wallet fund's balance floor, a transaction type not enabled for the tenant, a per-transaction or daily issuance cap, or an operation on a frozen wallet.
Unexpected server error.