Add region and currencies list to grid customers

openapi/components/schemas/customers/Customer.yaml

@@ -15,6 +15,21 @@ properties:
     example: 9f84e0c2a72c4fa
   customerType:
     $ref: ./CustomerType.yaml
+  region:
+    type: string
+    description: >-
+      Country code (ISO 3166-1 alpha-2) representing the customer's regional identity
+      and regulatory jurisdiction.
+    example: US
+  currencies:
+    type: array
+    items:
+      type: string
+    description: >-
+      List of currency codes enabled for this customer.
+    example:
+      - USD
+      - USDC
   umaAddress:
     type: string
     description: >-

openapi/components/schemas/customers/CustomerCreateRequest.yaml

@@ -9,6 +9,29 @@ properties:
     example: 9f84e0c2a72c4fa
   customerType:
     $ref: ./CustomerType.yaml
+  region:
+    type: string
+    description: >-
+      Country code (ISO 3166-1 alpha-2) representing the customer's regional identity.
+      This determines the regulatory jurisdiction and KYC requirements for the customer.
+      Required if the customer will use currencies with different KYC requirements across
+      regions. A customer with accounts in multiple regions should be registered as separate
+      customers. This field is immutable after creation.
+    example: US
+  currencies:
+    type: array
+    items:
+      type: string
+    description: >-
+      List of currency codes the customer will use (ISO 4217 for fiat, e.g. "USD", "EUR";
+      tickers for crypto, e.g. "BTC", "USDC"). Required if the customer will use more than
+      one sending currency, since the correct currencies cannot always be inferred. If not
+      provided, currencies will be inferred from the customer's region. Some currency
+      combinations may require separate customers — if so, the request will be rejected
+      with details.
+    example:
+      - USD
+      - USDC
   umaAddress:
     type: string
     description: >-