{primaryLogo ? 
setLogoStage(logoStage + 1)} style={{
width: "3.5rem",
height: "3.5rem",
borderRadius: "0.5rem",
margin: 0,
flexShrink: 0
}} /> : }
{methodsCount > 0 || countries > 0 || currencies > 0 || highlights.length > 0 ?
{title}
{chipLabel ?
{chipLogoFailed || !chipLogo ? null : 
setChipLogoFailed(true)} style={{
width: "1rem",
height: "1rem",
borderRadius: "0.2rem",
margin: 0
}} />}
{chipLabel}
: null}
{category ? {category} : null}
{flowLabel ? {flowLabel} : null}
{methodsCount > 0 ? renderStat("Payment methods", methodsCount, "supported-payment-methods") : null}
{}
{countries > 0 ? renderStat("Countries", countries >= 200 ? "No limit" : countries, "supported-countries") : null}
{currencies > 0 ? renderStat("Currencies", currencies >= 150 ? "No limit" : currencies, "supported-currencies") : null}
{highlights.length > 0 ?
: null}
Highlights
{highlights.map(h =>
{h.label}
)}
{anchors.capabilities ?
All capabilities →
: null}
: null}
### APM credentials
When setting up Stripe APMs in the dashboard, configure the following credentials:
* **Webhook secret**: Find this in the Stripe Dashboard within Developer Settings under **Webhooks** once webhooks have been configured.
* **Stripe connected account**: Set this when using Stripe Connect. See [Stripe Connect](#stripe-connect) below.
* **Publishable key**: Used to initialize the Gr4vy hosted web page on a redirect.
## Stripe Connect
Stripe Connect lets a platform account make API calls on behalf of a connected merchant account. This configuration is optional. Leave it empty for standard (non-Connect) integrations where all transactions run directly on the platform account.
### Credential field
Most Stripe connectors expose a **Stripe connected account** field in the connection settings. Setting it applies the connected account to every operation on that connection.
### Per-transaction override
To route individual transactions to different connected accounts, pass the connected account as a connection option when creating a transaction.
```json theme={"system"}
{
"connection_options": {
"stripe-card": {
"stripe_connect": {
"stripe_account": "acct_1OcAyNGbm1cKE2pL"
}
}
}
}
```
When present, the per-transaction value takes precedence over the credential field for that operation.
Routing individual transactions to a different account can have undesired side effects (see webhooks below).
### Webhooks with Stripe Connect
When a connected account is configured, incoming webhooks are matched against the configured Stripe account. Events that belong to a different account are rejected. If you process payments across multiple connected accounts, configure a separate Stripe connection for each account with the matching connected account ID.