Update funding config
Changed onCreates or replaces the project's funding configuration.
Request
- Base URL: https://api.openfort.io
- URL: https://api.openfort.io/v2/funding/config
- Auth: one of:
- HTTP bearer
- HTTP bearer
Request body
Enabled web2 methods (FundingMethod values), in display order.
Whether native wallet pay (Apple/Google Pay) is offered. Needs the project's own CDP keys.
Whether the Stripe rail is offered. With the project's own Link OAuth client it runs in-page (embedded); without one it degrades to the hosted popup on the project's secret key alone.
Whether Coinbase hosted-checkout popup rows (including the rest-of-world fallback) are offered.
Null and omitted both mean "no recommended amount".
Follows the credential rules, since it belongs to the same Stripe account: omit to keep what is stored, send an empty string to clear it.
Response
Funding config saved.
Enabled web2 methods (FundingMethod values), in display order.
Whether native wallet pay (Apple/Google Pay) is offered. Needs the project's own CDP keys.
Whether the Stripe rail is offered. With the project's own Link OAuth client it runs in-page (embedded); without one it degrades to the hosted popup on the project's secret key alone.
Whether Coinbase hosted-checkout popup rows (including the rest-of-world fallback) are offered.
The project's Stripe publishable key, handed to the client so the embedded component can initialize. Public by design — it belongs to the same Stripe account as the embedded credentials below, so it is per-project too.
The project's CDP key pair is set (webhook secret is separate and optional).
The project's Stripe secret key is set (webhook secret is separate and optional).
The project's Stripe secret key AND Link OAuth client are set — the embedded in-page rail is unlocked. Without the optional Link OAuth client, Stripe runs through the hosted popup on the secret key alone.
Changes
- info
endpoint added
- info