Update platform configuration
Update platform configuration settings. cardConfigs can establish platform-level per-transaction and UTC-calendar-day card caps. Grid enforces the lower of each platform cap and its corresponding card-specific value without replacing the card-specific value. Daily limits reset at 00:00 UTC.
Authorizations
API token authentication using format <api token id>:<api client secret>
Body
"mycompany.com"
"https://api.mycompany.com/webhooks/uma"
Update or create the embedded-wallet configuration for this platform. Fields omitted from the nested object are left unchanged. Omit this field at the top level to leave the embedded-wallet configuration unchanged entirely.
Update card-tokenization authentication branding and delivery settings. Fields omitted from the nested object are left unchanged. Changes apply to subsequent delivery attempts.
Update platform-level card settings. Fields omitted from the nested object are left unchanged. For either spending limit, supply null to clear the platform cap or a positive integer to set it. Omit this field at the top level to leave all card settings unchanged.
Merge-by-key upsert of platform fee configs. A cross-currency transaction
fee config is keyed by (feeType, sourceCurrency) and a rail fee config by
(feeType, rail, direction, originator). Setting variable and fixed fees
to 0 for an existing config deactivates it. Omit this field to leave fee
configs unchanged.
A fee charged for a cross-currency transaction. There can be at most one cross-currency transaction fee config for a given source currency. The fee will apply to all cross-currency transactions that originate in the source currency.
- Option 1
- Option 2
Response
Configuration updated successfully
System-generated unique identifier
"PlatformConfig:019542f5-b3e7-1d02-0000-000000000003"
UMA domain for this platform
"platform.uma.domain"
The subdomain that incoming requests will be proxied to
"platform"
URL where webhook notifications will be sent
"https://api.mycompany.com/webhooks/uma"
List of currencies supported by the platform. This is what the platform's customers are able to hold, send, and receive.
Whether the platform is a regulated financial institution. This is used to determine if the platform's customers must be KYC/KYB'd by Lightspark via the KYC link flow. This can only be set by Lightspark during platform creation.
false
Embedded-wallet branding and OTP settings for this platform. Present only when the platform has configured embedded-wallet support; omitted otherwise.
Branding and sender configuration for card-tokenization authentication messages. This configuration is independent of embedded-wallet support.
Platform-level settings for cards issued by this platform.
Platform-collected fees that should be added on top of Grid-collected fees. Contains every currently-active fee config for the platform.
A fee charged for a cross-currency transaction. There can be at most one cross-currency transaction fee config for a given source currency. The fee will apply to all cross-currency transactions that originate in the source currency.
- Option 1
- Option 2
Creation timestamp
"2025-06-15T12:30:45Z"
Last update timestamp
"2025-06-15T12:30:45Z"