counterparty-requirements

Counterparty validation is performed by running a synchronous decision over stored provider data to check KYC and account verification. Use the validate_counterparty command with the provider ID and provider data JSON to determine necessary onboarding steps.

Quote generation requires validated provider and customer data to ensure all counterparty requirements, including KYC checks and payment account verifications, are met. The Skill synchronously validates this data before enabling the creation of a quote.

Yes, this is intended for payment service providers and enterprises managing multi-provider counterparty validation. It synchronously validates stored provider data to facilitate KYC checks and account verifications across various providers.

KYC and account verification statuses are checked by validating counterparty requirements synchronously. Execute the validate_counterparty command with the specific provider ID and its associated data JSON to facilitate these checks.

Synchronous counterparty validation operates over stored provider data, meaning it processes requirements as a blocking decision. It is designed for validating existing provider data, KYC checks, and account verifications rather than asynchronous data collection.

Yes, counterparty validation includes advanced flow collection to determine necessary onboarding steps. It synchronously validates stored provider data to manage KYC, account verification, and quote generation processes.