Skip to main content

User not found

Error code​

{
  "code": "user.not_found",
  "docUrl": "https://doc.mor.payments.ai/errors/user-not-found"
}

HTTP status​

404

Cause​

On assign member (POST /v1/public-api/merchants/{merchantId}/members), this response is returned when the email does not match any Payments AI user or when the user exists but is not an active member of your merchant team (the merchant that owns the API key). Both cases return the same response so callers cannot tell whether an address is registered.

On dashboard auth flows, the same code can mean your profile row is missing or a linked identity is not associated with your account.

How to fix​

For Public API assign:

  1. Confirm the person has signed up in Payments AI and is an active member of your merchant team (dashboard Team).
  2. Use the exact email on that membership.
  3. If you need someone who is not on your team yet, invite them to your merchant in the dashboard first, then call assign to copy them onto the sub-merchant.

POST /v1/public-api/merchants/{merchantId}/members — see Partner Onboarding.