docs(sca): document Strong Customer Authentication for EU customers

.redocly.lint-ignore.yaml

@@ -6,6 +6,14 @@ openapi.yaml:
   no-required-schema-properties-undefined:
     - '#/components/schemas/QuoteSource/required/0'
     - '#/components/schemas/Quote/properties/destination/required/0'
+    # anyOf proof-requirement branches reference properties defined at the
+    # parent schema level (valid JSON Schema; the rule is overly strict here).
+    - '#/components/schemas/ScaLoginCompleteRequest/anyOf/0/required/0'
+    - '#/components/schemas/ScaLoginCompleteRequest/anyOf/1/required/0'
+    - '#/components/schemas/ScaLoginCompleteRequest/anyOf/1/required/1'
+    - '#/components/schemas/BeneficiaryTrustConfirmRequest/anyOf/0/required/0'
+    - '#/components/schemas/BeneficiaryTrustConfirmRequest/anyOf/1/required/0'
+    - '#/components/schemas/BeneficiaryTrustConfirmRequest/anyOf/1/required/1'
   no-invalid-media-type-examples:
     - >-
       #/paths/~1customers~1external-accounts/post/requestBody/content/application~1json/schema

mintlify/docs.json

@@ -58,6 +58,17 @@
               "platform-overview/core-concepts/currencies-and-rails",
               "platform-overview/configuration"
             ]
+          },
+          {
+            "group": "Strong Customer Authentication",
+            "pages": [
+              "platform-overview/sca/overview",
+              "platform-overview/sca/per-transaction-authorization",
+              "platform-overview/sca/factor-enrollment",
+              "platform-overview/sca/login-and-sessions",
+              "platform-overview/sca/trusted-beneficiaries",
+              "platform-overview/sca/two-factor-reset"
+            ]
           }
         ]
       },

mintlify/global-p2p/sending-receiving-payments/sending-payments.mdx

@@ -27,4 +27,13 @@ import SendUMA from '/snippets/sending/uma.mdx'
 
 <SendUMA />
 
+## Strong Customer Authentication (EU customers)
+
+Customers in SCA-regulated regions (in practice the EU: EUR / USDC) must confirm
+payments with Strong Customer Authentication. When it applies, the payment comes
+back `PENDING_AUTHORIZATION` with an `scaChallenge` that you authorize before the
+transfer is released; for every other customer nothing changes. See
+[Per-transaction authorization](/platform-overview/sca/per-transaction-authorization)
+for the full walkthrough.
+