Business Profiles

A business profile is a config block under a merchant account that controls how payments are processed for a given line of business: which connectors to try, where to redirect customers (return_url), where to deliver webhooks, what fraud rules apply, and how payment links are branded.

A merchant has at least one business profile (the default, created automatically) and can have many. Each payment is associated with exactly one profile via the profile_id field on the create payment request — that profile's config is what the router uses while processing.

Why profiles matter for direct API integration

Several fields you might expect on individual payment endpoints actually live here:

• return_url — the URL the customer is redirected to after off-site flows finish. Configured once per profile, applied to every payment under it.
• webhook_details — the URL plus credentials the platform calls when payment status changes.
• payment_link_config — the default branding the payment-links endpoint inherits when no per-link override is sent.
• is_auto_retries_enabled / max_auto_retries_enabled — whether the platform should retry a declined payment on a fallback connector.
• card_testing_guard_config — fraud rules to block card-testing patterns (IP, customer, guest user thresholds).
• fraud_ml_mode — how the fraud ML model should be applied (off, passive, active).

Endpoints