A consent field is invalid

Description

A field of the consent object breaks its shape rule while the subaccount's consent policy is enforce, so the card is not enrolled. detail has the form consent.<field> is invalid: <rule> and names the field and the rule, never the value you sent. Common causes: no text on the api channel, a blank or too long text, a locale that is not a BCP 47 tag, or a card number in text, customerTermsText or locale (such a value is never stored).

POST /card-subscriptions answers 400:

{
  "detail": "consent.text is invalid: Must not contain a card number",
  "title": "Consent record invalid",
  "type": "https://docs.astrada.co/reference/errors-consent_invalid",
  "errorCode": "card_subscription.consent_invalid"
}

How to solve

Correct the field detail names and retry. If your text holds an example card number, remove it. Each field's rules: Send the consent record.