Capture Payment Intent
Authentication
Standard Basic HTTP authentication. The username is the Fluveo secret key and the password must be empty, encoded as base64(api_key:).
Bearer HTTP authentication. Allowed header: Authorization: Bearer <api_key>.
Path parameters
Headers
Makes a POST safely retryable according to that operation’s documented idempotency policy. The durable 24-hour journal applies only where the resource documentation explicitly claims it. Reusing a key with different parameters or another endpoint returns an idempotency error.
Request
Stripe-compatible public metadata: at most 50 merchant-visible entries, with keys up to 40 characters and string values up to 500 characters. Server-owned fluveo_ stamps are not part of the public allowance and are never returned.
Refused on capture with a 400 naming this parameter: no Fluveo capture connector sends a descriptor, so it would be dropped. Set it when you create or update the PaymentIntent.
Response
Stripe-compatible response
Fluveo narrowing: not in upstream pin; truthful public id-prefix constraint: pi_.
Test-mode redirect action. redirect_to_url.url sends the customer to authenticate; after completion the customer is redirected to redirect_to_url.return_url.
Fluveo narrowing annotation: truthful single-value public object constant.