Skip to content

Update Card Verification Email ​

POST /openapi/v2/cards/{cardId}/3ds-contact/email

Uses existing OpenAPI signing. cardId is the card identifier returned by card queries, not a full card number or database primary key. Only cards owned by the credential tenant are accessible.

Send application/json. Update one contact at a time. This changes only this card’s verification recipient, not login email, KYC or other cards, and does not send a verification code. Confirm cardholder authorization and ownership before submitting.

Request body ​

FieldTypeRequiredDescription
requestNostringYes1–64 letters, digits, underscores or hyphens; unique within this tenant and operation family.
emailstringYesOne valid email address, up to 254 characters.
ownershipVerifiedbooleanYesMust be true: caller attests authorization and ownership verification; this is not platform OTP verification.
json
{
  "requestNo": "contact_email_001",
  "email": "holder@example.com",
  "ownershipVerified": true
}

Operation fields ​

For updates these are the fields of data; for queries they are operations[].

FieldTypeDescription
operationNostringPlatform operation identifier.
requestNostringCaller idempotency key.
fieldstringEMAIL or PHONE.
targetMaskedstringMasked requested contact.
statusstringUNKNOWN, ACCEPTED, CONFIRMED, FAILED.
providerCodestring/nullSafe channel result code, nullable.
createdAtstringCreation time.
updatedAtstringUpdate time.

Status and retries ​

  • The outer code=200 means the platform handled the request, not that the contact is effective.
  • UNKNOWN: submission may still be in flight or its result is uncertain. ACCEPTED: channel accepted the update, effectiveness is not confirmed. Both block other updates to this card.
  • CONFIRMED: the platform verified external evidence that the update took effect. FAILED: definitive rejection or externally verified failure. Either permits a new update.
  • Same requestNo and content returns the existing operation; changed content returns UCARD_REQUEST_CONFLICT. Do not change keys to bypass an unresolved result. Query the existing record to trigger automatic verification. Contact platform support if the result remains unresolved; OpenAPI has no manual resolve endpoint.
  • Unsupported edits return UCARD_CONTACT_UNSUPPORTED; pending operations return UCARD_CONTACT_PENDING; invalid data returns UCARD_CONTACT_INVALID. These identifiers appear in msg, not as a replacement for the outer numeric code.