Error codes

The stored account-provisioning configuration is not supported by this application release.

Fix: Contact Flint support to repair the account setup configuration before retrying.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

A failed provider refund already exists for this Affirm payment.

Fix: Do not create a new provider refund. Use an alternative reimbursement and reconcile the failed Refund.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The API key exists but is past its expiration time.

Fix: Create or use an active API key for the target mode and merchant, then retry.

The API key is not usable for its stored payment-mode binding.

Fix: Create or use an API key whose mode matches the target environment, then retry.

No API key matches the provided credential.

Fix: Check the API key value or create a new API key, then retry.

The request did not include an API key or accepted bearer credential.

Fix: Send a Flint API key in X-API-Key or as Authorization: Bearer <API_KEY>, then retry.

The API key exists but has been revoked.

Fix: Create or use an active API key for the target mode and merchant, then retry.

The API key is bound to a sandbox that is missing, archived, inactive, or mode-incompatible.

Fix: Create or use a sandbox-bound test key for an active sandbox, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The API key uses a legacy or unsupported scope grant.

Fix: Create a new API key with explicit public API scopes, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be authenticated.

Fix: Send a valid Flint API key, partner install token, checkout session credential, or dashboard session for this route, then retry.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

Buyer credentials cannot set merchant-owned fulfillment correlation fields.

Fix: Remove external_system and external_reference. Set merchant correlation from a server-authenticated request.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The requested onboarding capability combination is not supported by Flint's current merchant-account configuration.

Fix: Request accept_card_payments and receive_payouts together. You may also include accept_ach_debit_payments, or omit requested_capabilities to use the default set.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The requested capture exceeds the authorization's current capturable amount.

Fix: Use an amount no greater than capturable_money, or omit amount_money to capture the available authorization.

The requested capture currency differs from the authorization currency.

Fix: Send amount_money in the capturable authorization currency.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Coupon entry is disabled for this checkout session.

Fix: Continue without a coupon or start a checkout session with coupon entry enabled.

Checkout authentication was rotated before payment work became durable.

Fix: Refresh the checkout session through its owning invoice or checkout entry point, then resume the same payment attempt if it remains available.

Checkout buyers cannot apply discounts by resource ID.

Fix: Provide the buyer-facing coupon or promotion code instead.

Checkout buyers can remove only coupon or promotion-code discounts.

Fix: Remove a buyer-applied code discount or ask the merchant to change other discounts.

The checkout launch credential is scoped to hosted checkout bootstrap and cannot authorize public API operations.

Fix: Open the hosted checkout URL so Flint can exchange the launch credential for a checkout session credential.

Checkout buyers cannot create manual discounts.

Fix: Apply a coupon or promotion through checkout, or create the manual discount with merchant authentication.

Checkout payment work is still resolving, so the competing change cannot proceed yet.

Fix: Wait briefly, then retry the same request after the payment attempt converges.

The expired checkout session is in constrained recovery mode and the request targets a different payment attempt.

Fix: Read or resume only the payment attempt identified by the checkout session recovery response.

The expired checkout session is in constrained recovery mode and cannot perform this operation.

Fix: Read the order or owning payment attempt, or resume that exact payment attempt before the recovery deadline.

replace_checkout_session_id is only valid when creating an order-backed checkout session.

Fix: Send replace_checkout_session_id together with order_id, without quick_pay_item or plan_id.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

An open checkout session already exists for this order.

Fix: Reuse the session identified by existing_checkout_session_id, or send that ID as replace_checkout_session_id to replace it atomically.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The session named by replace_checkout_session_id is no longer the order's current open session.

Fix: Read the session identified by current_checkout_session_id, then retry replacement against that ID if a new session is still needed.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

The resource is available to checkout authentication only after the checkout session is paid.

Fix: Complete payment, then retry with the same checkout session credential.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The checkout credential is bound to a different checkout session.

Fix: Use the credential issued for this checkout session.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

Tipping is disabled for this checkout session.

Fix: Continue without a tip or start a checkout session with tipping enabled.

The requested tip is not available for this checkout session.

Fix: Choose one of the checkout session's configured tips or enable custom tipping.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The ConfirmationToken contains a malformed payment return URL.

Fix: Create a new ConfirmationToken using the exact payment_collection.stripe.return_url.

The ConfirmationToken return URL does not match this payment's active Flint relay.

Fix: Create a new ConfirmationToken using the exact payment_collection.stripe.return_url for this payment.

The ConfirmationToken does not contain Flint's payment return relay URL.

Fix: Create a new ConfirmationToken using the exact payment_collection.stripe.return_url.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The webhook stream resume values disagree.

Fix: Send either Last-Event-ID or after_event_id, or make both values identical.

Customer account resources are temporarily unavailable.

Fix: Retry with exponential backoff.

The customer account resource was not found for this customer.

Fix: Check the resource ID. Customer-session routes never reveal another customer's resources.

The customer still has subscriptions or saved payment methods that could remain operational after account deletion.

Fix: Cancel every non-canceled subscription and remove every saved payment method, then retry approval.

The requested email is already associated with another customer for this merchant.

Fix: Use a different email address or reconcile the duplicate customer records.

Customer sessions are temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The customer session use window expired.

Fix: Refresh the customer session with its refresh token, then retry with the new secret.

The customer or customer session was not found in the selected merchant environment.

Fix: Check the resource ID and selected environment.

The customer session refresh token is invalid or expired.

Fix: Authenticate the buyer again and mint a new customer session.

A rotated customer session refresh token was presented again, so the session family was revoked.

Fix: Authenticate the buyer again and mint a new customer session.

The endpoint requires a customer session bearer credential.

Fix: Send the customer session secret in the Authorization bearer header.

The customer account custom hostname has not completed domain validation.

Fix: Create and validate the hostname as a payment method domain before saving it as the customer account domain.

The request exceeded a Flint rate or usage limit.

Fix: Retry with exponential backoff and jitter. Use the Retry-After header when present.

A public resource referenced another resource that could not be resolved during expansion.

Fix: Contact support with the request_id; this indicates a Flint data-integrity defect.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The calculation behind the delivery selection expired before payment began.

Fix: Create a new delivery quote, select a current option, and retry payment.

This checkout requires a rate supplied by the merchant server.

Fix: Create the delivery quote from the merchant server and then let the buyer select from the resulting options.

The selected delivery obligations require incompatible commerce treatment.

Fix: Change the delivery method or obligation configuration so the selected quantities share compatible tax, currency, and destination treatment.

The delivery configuration does not satisfy its typed contract.

Fix: Fix the field identified by the response and retry.

A pinned delivery dependency was revoked and can no longer authorize a new quote or selection.

Fix: Publish or select a replacement configuration revision, then create a new quote.

The delivery destination is invalid.

Fix: Fix the destination field identified by the response and retry.

The checkout delivery eligibility context changed after the request basis was read.

Fix: Read the current eligibility revision and retry.

The current delivery selection basis is required.

Fix: Send the current delivery selection ID, or null when no selection exists.

The expected_version write fence is not a positive integer.

Fix: Read the current resource, then retry with its version as expected_version.

This configuration change requires an explicit expected_version write fence.

Fix: Read the current resource, then retry with its version as expected_version.

The delivery external reference is already bound to another selection.

Fix: Reuse the existing selection or submit a new external reference.

The request includes a field that does not apply to this delivery resource.

Fix: Remove the field identified by param and retry.

The request omits a field required by this delivery resource.

Fix: Provide the field identified by param and retry.

The delivery obligations cannot form a valid set of buyer choices.

Fix: Change the assigned delivery profiles, origin policies, or splitting rules before creating another quote.

This delivery input requires merchant authentication.

Fix: Create the quote from the merchant server with an API key.

The payment link has no line item that can use a delivery method.

Fix: Clear delivery_method_ids, or use a catalog-backed line item with an applicable delivery profile.

Delivery method assignment is temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The selected delivery option belongs to another selection.

Fix: Read the current selection, then retry with its ID as the compare-and-swap value.

The selected delivery option or its guarantee expired.

Fix: Create a new delivery quote and select a current option.

The selected option does not belong to the specified choice group.

Fix: Use an option ID from the same choice group in the quote response.

Checkout delivery authority changed during pickup evaluation.

Fix: Read the current delivery selection and retry with its ID.

The pickup availability input is invalid.

Fix: Fix the field identified by the response and retry.

Flint could not construct trustworthy pickup availability evidence.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The requested pickup location is not available for the configured delivery methods.

Fix: Choose a pickup location from the configured collection and retry.

The delivery preview input is invalid.

Fix: Fix the field identified by the response and retry.

The requested methods cannot fulfill at least one line item's allowed fulfillment types.

Fix: Change delivery_method_ids or line_items[].fulfillment.allowed_types so at least one requested method supports each line item.

The requested preview depends on checkout-only state.

Fix: Create or update a checkout session, then request a checkout delivery quote.

Flint could not construct trustworthy cart, routing, or dependency lineage for the preview.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The pending quote no longer matches the supplied checkout inputs.

Fix: Create a new quote from the current checkout inputs.

The delivery quote or one of its options expired.

Fix: Create a new delivery quote and select a current option.

The delivery quote still requires caller input or rates.

Fix: Supply every input or caller-supplied method result requested by the pending quote.

The selected destination conflicts with address facts used by the quote.

Fix: Create a new delivery quote using the selected destination.

The delivery quote input is invalid.

Fix: Fix the field identified by the response and retry.

The delivery quote was revoked.

Fix: Create a new quote.

The quote no longer matches the current checkout authority.

Fix: Create a new delivery quote and retry the selection.

Flint could not calculate a delivery quote.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The delivery request does not satisfy the endpoint contract.

Fix: Fix the field identified by the response and retry.

Active resources depend on this delivery resource.

Fix: Remove the dependencies described by the response before retrying the lifecycle change.

The delivery resource does not exist in the authenticated merchant environment.

Fix: Check the resource ID and environment, then retry.

The delivery resource changed before the requested revision was published.

Fix: Read the current resource version, reapply the intended change, and retry.

The current delivery selection changed after the request basis was read.

Fix: Read the effective selection, create a replacement-basis quote, and retry with its exact selection ID.

The delivery selection expired before payment began.

Fix: Create a new delivery quote, select a current option, and retry payment.

The selection does not choose one option for every choice group.

Fix: Submit exactly one choice for every choice group in the quote.

This checkout reached its protected delivery selection history limit.

Fix: Finish or restart the checkout. Terminal private payloads become eligible for redaction after their retention period.

Delivery selection is temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Fulfillment configuration is temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The delivery resource is not in a state that allows the operation.

Fix: Read the current resource and choose an operation valid for its lifecycle state.

The requested delivery resource status is invalid.

Fix: Use active or inactive when creating a delivery method.

The selected delivery window expired.

Fix: Create a new delivery quote and select a current window.

The selected window was not offered by the chosen delivery option.

Fix: Use a delivery_window_id from the selected option, or omit it when the option does not require a window.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The demo session key cannot access this route.

Fix: Use a merchant API key for this route, or call a route supported by demo sessions.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Developer resource management requires a live API key.

Fix: Use a live management key from Dashboard, Developers, API keys.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request includes the same scope more than once.

Fix: Remove the duplicate scope and retry.

The request includes the same tax breakdown more than once.

Fix: Provide each tax_breakdown_id once.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The email change confirmation window expired.

Fix: Request a new email change confirmation.

The email change confirmation code is invalid.

Fix: Enter the latest code sent to the new address.

The email change confirmation could not be delivered.

Fix: Retry the request. The current customer email remains unchanged.

The customer requested too many email changes within 15 minutes.

Fix: Wait 15 minutes, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Embedded checkout needs a clean merchant return destination for redirect payment options.

Fix: Set redirects.success_redirect_url to the HTTPS storefront URL that should recover this checkout.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

A service required for an accepted expansion is unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The requested expansion exceeded a route fanout or response-size limit.

Fix: Request fewer expansions or use follow-up read/list endpoints.

Flint could not resolve an accepted expansion.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

A transaction image referenced an external URL instead of a Flint-owned canonical image.

Fix: Ingest the image on an image-bearing resource, then use the untransformed image.url returned by Flint.

The authenticated caller is not allowed to set this field or value.

Fix: Remove the field or use a caller authorized for that operation, then retry.

A required request field is missing.

Fix: Supply the field named by param and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The flat tax is not fully attributable to refundable payment settlements.

Fix: Read the order payment state and retry after every payment settlement is available.

A flat tax must be refunded for its full remaining amount or omitted.

Fix: Set tax_money to the full remaining flat tax amount, or omit this tax breakdown.

Stored flat-tax refund lineage is inconsistent with whole-or-nothing reversal.

Fix: Contact support with the request_id so Flint can repair the refund lineage.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

This fulfillment requires explicit merchant approval before work begins.

Fix: Accept the fulfillment, then advance it into preparation, movement, or completion.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The fulfillment command reason is not valid for this action.

Fix: Use one of the reason values documented for the command and retry.

An ad-hoc line item is missing its explicit fulfillment requirement.

Fix: Provide the line item's fulfillment object and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

This checkout requires a delivery selection before payment can begin.

Fix: Create a current delivery quote, select one option for every choice group, then retry payment.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

A request with the same idempotency key is still in progress.

Fix: Wait briefly and retry with the same idempotency key.

This operation requires an idempotency key.

Fix: Send a unique Idempotency-Key header and reuse it for retries of the same logical operation.

The idempotency key was reused with a different request body.

Fix: Use the original request body with this idempotency key, or generate a new idempotency key for a new operation.

The idempotency key exceeds the supported length.

Fix: Send an Idempotency-Key header no longer than 255 characters.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The payment-link resolution with this context and idempotency key is still in progress.

Fix: Wait briefly and retry with the same resolution_context and Idempotency-Key.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The image gallery replacement omitted its required images field.

Fix: Send images as an array. Use an empty array to clear the gallery.

The image source is animated, but Flint accepts still images only.

Fix: Provide a still JPEG, PNG, or WebP image, then retry.

The canonical image has expired or was deleted.

Fix: Re-supply the original source_url on a catalog or branding resource.

The canonical image does not exist in the authenticated merchant and environment, or is not attachable.

Fix: Use an untransformed image.url returned for this merchant and environment, then retry.

The image dimensions exceed Flint's axis or pixel limits.

Fix: Resize the source to at most 12,000 pixels per axis and 40 megapixels, then retry.

The image format is unsupported or malformed.

Fix: Provide a valid still JPEG, PNG, or WebP image, then retry.

The requested gallery contains more than eight images.

Fix: Send no more than eight images in the gallery.

The image gallery service is not available in this server configuration.

Fix: Retry after the service configuration is restored.

The mutation contains more external image ingestions than one request allows.

Fix: Split the change into mutations containing at most 32 external image sources.

The prior image ingestion expired and its reserved storage was cleaned up.

Fix: Retry the request with a new idempotency key.

The same image ingestion step is still running.

Fix: Wait briefly, then retry with the same idempotency key and request body.

The prior image ingestion attempt ended and cannot be resumed.

Fix: Wait briefly for cleanup, then start a new ingestion with a new idempotency key.

The mutation exceeds the total decoded image pixel budget.

Fix: Resize the sources or split the images across smaller mutations.

Image processing capacity is temporarily exhausted.

Fix: Retry with exponential backoff. If remediation says to start a new ingestion, use a new idempotency key.

The image could not be decoded or processed safely.

Fix: Replace an invalid source. If remediation says to start a new ingestion, use a new idempotency key.

Image processing exceeded its deadline.

Fix: Retry with exponential backoff and a new idempotency key when remediation says to start a new ingestion.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The source did not return a complete supported image response.

Fix: Check the source response, redirects, encoding, and content length, then retry.

The source URL does not resolve to an allowed public origin.

Fix: Use a public HTTPS origin that does not resolve to private, loopback, link-local, or Flint infrastructure addresses.

The source host did not return the image before the fetch deadline.

Fix: Retry with exponential backoff and a new idempotency key when remediation says to start a new ingestion, or use a more reliable source host.

The source image exceeds the 5 MB byte limit.

Fix: Reduce the source file below 5 MB, then retry.

The source host was temporarily unavailable.

Fix: Retry with exponential backoff and a new idempotency key when remediation says to start a new ingestion.

The image source URL violates Flint's HTTPS source rules.

Fix: Use an HTTPS URL on port 443 without credentials or a fragment.

The merchant's stored image bytes have reached the configured quota.

Fix: Remove unused image attachments or wait until ready unattached images expire, then retry.

The submitted image URL is invalid.

Fix: Use the exact untransformed image.url returned by Flint.

The image URL is a transformed delivery URL instead of the canonical asset URL.

Fix: Use the exact image.url returned by Flint without a variant path, query, or fragment.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The API key is missing a required scope.

Fix: Create or use an API key with the required scope, then retry the request.

Flint returned an internal server error.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The API key credential is malformed or invalid.

Fix: Check the API key value or create a new API key, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The Authorization header is malformed or uses an unsupported credential.

Fix: Send a Flint API key or partner install token as Authorization: Bearer <token>, or use X-API-Key for API keys.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The cancellation reason is not in the supported public vocabulary.

Fix: Use requested_by_customer, duplicate, fraudulent, or abandoned as allowed for the caller.

The requested capture amount is invalid.

Fix: Send a positive amount in the authorization currency, or omit amount_money to capture the available authorization.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The checkout surface is invalid.

Fix: Send surface as hosted or embedded.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The order payment completion behavior is invalid.

Fix: Use complete_order or partial_payment and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

created_after is not a valid RFC 3339 timestamp.

Fix: Send an RFC 3339 timestamp or omit created_after.

created_before is not a valid RFC 3339 timestamp.

Fix: Send an RFC 3339 timestamp or omit created_before.

created_before must not be earlier than created_after.

Fix: Correct the creation-time range and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The webhook stream resume event ID is malformed.

Fix: Use a webhook_event_id previously returned by the stream, or omit the resume value.

A customer account resource request is invalid.

Fix: Correct the invalid fields and retry.

The customer session request contains an invalid lifetime or omits its customer.

Fix: Fix the field described by the error and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The delivery configuration status filter is invalid.

Fix: Use configured or action_required.

evaluation_status is not a supported delivery quote evaluation status.

Fix: Use complete, incomplete, or degraded.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The delivery profile ID is invalid.

Fix: Use a valid dprof_ ID.

status is not a supported delivery quote status.

Fix: Use active, consumed, stale, expired, or revoked.

The requested webhook delivery status is not supported.

Fix: Use pending, delivered, failed, or suppressed and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The payment method domain name is not an exact fully-qualified hostname.

Fix: Send one domain or subdomain without a scheme, path, port, IP address, or wildcard.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request included an invalid or unsupported expand path.

Fix: Fix or remove the requested expand path; use only supported values documented for the route.

The request included an invalid or past expiration timestamp.

Fix: Send expires_at as a future RFC3339 timestamp, or omit it for a non-expiring key.

The request payload contains a field with the wrong JSON type.

Fix: Send the field using the documented JSON type, then retry with the same idempotency key if this was the same logical operation.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The inline fulfillment requirement is invalid.

Fix: Fix the identified fulfillment field and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The image alt text exceeds the supported length.

Fix: Shorten alt to 512 characters or fewer, then retry.

The image external reference ID has an invalid length.

Fix: Use a non-empty external_reference_id of at most 255 characters, or omit it.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The report interval end is invalid.

Fix: Use an RFC 3339 instant for interval_end_at.

The report interval start is invalid.

Fix: Use an RFC 3339 instant for interval_start_at.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry with the same idempotency key if this was the same logical operation.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The max_amount filter is not a single positive integer in minor units.

Fix: Send max_amount once as a positive integer in minor units and include its three-letter currency, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The min_amount filter is not a single positive integer in minor units.

Fix: Send min_amount once as a positive integer in minor units and include its three-letter currency, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The requested origin is not supported.

Fix: Use a documented origin value and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The partner install token is invalid or expired.

Fix: Refresh or reinstall the partner app authorization, then retry with a valid partner install token.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The requested payment status is not supported.

Fix: Use unpaid, partially_paid, or paid and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The requested refund status is not supported.

Fix: Use none, partially_refunded, or refunded and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The report interval is invalid.

Fix: Set interval_end_at after interval_start_at.

The report type is not supported.

Fix: Use a report_type listed in the reports reference.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request body is invalid.

Fix: Send valid JSON that matches the request schema and contains no unknown fields.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The report timezone is invalid.

Fix: Use an IANA timezone name such as America/New_York.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The transaction purpose is not supported.

Fix: Use goods, services, or other and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The merchant website URL is not valid for account onboarding.

Fix: Send the merchant's real, publicly reachable business website URL in profile.website_url, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The inventory adjustment was not found in this merchant environment.

Fix: Check the inventory adjustment ID and environment.

The inventory basis changed before the mutation committed.

Fix: Read the current revision or routing basis and retry with a new idempotency key when the logical request changes.

The requested inventory quantities violate a physical-condition invariant.

Fix: Correct the condition quantities and retry.

The inventory count or captured physical revision changed.

Fix: Read the current count and level revisions, then retry the count operation.

The inventory count was not found in this merchant environment.

Fix: Check the inventory count ID and environment.

Physical stock at this level changed after the count captured it.

Fix: Recount the affected inventory item at this location, then submit the observation again.

The physical inventory event provenance is structurally invalid.

Fix: Correct the event time, source system, external source, actor, or observation sequence and retry.

Current eligible inventory cannot satisfy the complete demand.

Fix: Change demand, replenish stock, or change the routing source before retrying.

The inventory item has active dependencies.

Fix: Remove the reported catalog, level, reservation, or transfer dependencies before archiving it.

The inventory resource was not found in this merchant environment.

Fix: Check the resource ID and environment.

The inventory item does not accept new sale or routing use.

Fix: Activate the item or use another active inventory item.

The inventory level was not found in this merchant environment.

Fix: Check the inventory level ID and environment.

The Location inventory capability rejects new claims.

Fix: Activate allocation for the Location or choose another Location.

The Location does not have an active inventory capability.

Fix: Configure and activate the Location inventory capability.

The inventory movement was not found in this merchant environment.

Fix: Check the inventory movement ID and environment.

The allocation policy request is structurally invalid.

Fix: Correct the policy groups, ordering, splitting behavior, or limits and retry.

The inventory allocation policy was not found in this merchant environment.

Fix: Check the inventory allocation policy ID and environment.

The requested reservation transition exceeds the eligible quantity.

Fix: Read the reservation lines and submit cumulative targets within the active quantities.

The replacement conflicts with the current source reservation.

Fix: Read the source reservation and retry against its current revision and active buckets.

The reallocation mapping is structurally invalid or does not conserve demand.

Fix: Correct the source buckets, replacement demands, Locations, and quantities and retry.

The inventory reallocation was not found in this merchant environment.

Fix: Check the inventory reallocation ID and environment.

The line-item inventory requirement is invalid.

Fix: Set inventory_requirement to not_tracked or tracked and provide matching demand lines.

An ad-hoc line item is missing its inventory requirement.

Fix: Set inventory_requirement explicitly to not_tracked or tracked.

The owner slot already has an active reservation.

Fix: Read or replace the active reservation identified by the conflict details.

The reservation is no longer an active stock claim.

Fix: Create a new route-and-hold reservation.

The inventory reservation was not found in this merchant environment.

Fix: Check the inventory reservation ID and environment.

The caller cannot mutate this reservation owner type.

Fix: Use the workflow that owns the reservation.

The inventory return receipt conflicts with current inventory lineage.

Fix: Read the linked consumed quantities and retry with a valid remaining return quantity.

The inventory return receipt request is structurally invalid.

Fix: Correct the receiving Location, disposition, lineage, and quantities and retry.

The inventory return receipt was not found in this merchant environment.

Fix: Check the inventory return receipt ID and environment.

Tracked demand requires an explicit inventory routing source.

Fix: Provide a fixed Location, active policy, or immutable policy version and retry.

The routing request exceeds a published structural limit.

Fix: Reduce the number of demand lines, assignment edges, policy Locations, or split Locations and retry.

A required routing dependency could not calculate authoritative ordering evidence.

Fix: Retry after the routing dependency recovers.

The requested committed quantity is not protected by physical stock.

Fix: Replenish, release, cancel, or explicitly reallocate the affected claim.

The physical observation sequence is stale or conflicting.

Fix: Read the accepted source sequence and submit a strictly newer absolute observation.

The inventory tracking declaration is invalid.

Fix: Set inventory_tracking to not_tracked or tracked and provide the matching inventory item relationship.

The inventory tracking declaration is required.

Fix: Set inventory_tracking explicitly to not_tracked or tracked.

The inventory transfer revision changed.

Fix: Read the current transfer and retry against its revision.

The inventory transfer request is structurally invalid.

Fix: Correct the Locations, lines, physical conditions, or cumulative targets and retry.

The inventory transfer was not found in this merchant environment.

Fix: Check the inventory transfer ID and environment.

Stock could not be held for this order's tracked line items.

Fix: Check availability for the order's routing source, then replenish, widen the allocation policy, or reduce the quantity.

The invoice balance changed after the payment request was prepared.

Fix: Refresh the invoice and rebuild the payment selection from its current collectible balance.

Invoice-owned checkout sessions cannot be replaced through generic checkout creation.

Fix: Use the invoice checkout-session endpoint to manage collection for an invoiced order.

The invoice collection state changed after the request was prepared.

Fix: Refresh the invoice, then rebuild the request from its current state.

The invoice has no active public link, so hosted collection or link delivery cannot proceed.

Fix: Regenerate the invoice public link, then retry.

The invoice is not open or partially paid with a balance remaining.

Fix: Collect only open or partially_paid invoices with a positive outstanding_money.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The invoice has not been sent, so it has no public link to manage.

Fix: Send the invoice first, then manage its public link.

Invoice payment work is still resolving, so competing collection or mutation cannot proceed yet.

Fix: Wait briefly, then retry the same request after the payment attempt converges.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The Location revision changed.

Fix: Read the current Location and retry against its revision.

A Location mutation conflicted with a current revision or active dependency.

Fix: Use the current revision or remove the reported dependency before retrying.

The Location geography revision changed.

Fix: Read the current Location geography and retry against its geography revision.

The Location geography input is structurally invalid.

Fix: Correct the address, timezone, coordinate, or coordinate source and retry.

The Location request is structurally invalid.

Fix: Correct the reported Location field and retry.

The Location inventory capability revision changed.

Fix: Read the current inventory capability and retry against its revision.

The Location has active dependencies.

Fix: Remove or close the reported dependencies before archiving the Location.

The Location is not active for a new dependency or claim.

Fix: Activate the Location or choose another active Location.

The Location was not found in this merchant environment.

Fix: Check the Location ID and environment.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

The merchant payment account is not ready for domain registration.

Fix: Complete merchant payment onboarding in the selected environment, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not read the merchant billing projection.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The route exists, but does not support the requested HTTP method.

Fix: Use one of the methods supported by the route, as listed in the Allow header.

The customer is determined by the customer session on every /v1/me route.

Fix: Remove customer_id from the query string and request body, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The normalized image exceeds Flint's canonical byte limit.

Fix: Reduce the source dimensions or complexity, then retry.

The selected flat tax has no refundable amount remaining.

Fix: Remove the tax breakdown from the request or read the order and its refunds before retrying.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The application release cannot resume the provider-account controller policy frozen on this onboarding attempt.

Fix: Restore support for the frozen controller policy version before retrying or deploying this release.

The direct merchant owner who initiated onboarding no longer authorizes initial provider-account setup.

Fix: Have the initiating direct owner retry, or restart before provider provisioning under the current direct owner.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

The account profile is managed through the embedded account experience after provider account setup begins.

Fix: Open an account-management session and edit the profile there.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The order is already closed.

Fix: Read the order and continue from its current terminal state instead of closing it again.

The order changed after the caller prepared its payment request.

Fix: Refresh the order or checkout session and rebuild the selected payment legs from current state.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Another collection flow is already active for this order.

Fix: Finish or close the collection flow that owns the order before starting another.

A checkout or invoice flow currently owns collection for the order.

Fix: Finish or close the owning collection flow before starting another order payment.

An open checkout already owns collection for the order, so customer authority cannot change under its issued credential.

Fix: Close or expire the checkout identified by existing_checkout_session_id, set customer_id on the order, then create a new checkout.

Delayed capture currently supports only one payment leg per order attempt.

Fix: Use a single manual-capture leg, or use automatic capture for split payment.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The selected payment intent is not owned by this order.

Fix: Create payment intents through the order-scoped route, then select those IDs, or use payment_source for a one-shot payment.

The order has lock-owning payment work in progress.

Fix: Read active_payment_attempt. Resume it only when is_resumable is true; otherwise cancel, capture, or resolve it as allowed.

The payment intent is owned by an order and cannot be managed through a standalone payment-intent action route.

Fix: Use the order payment flow to confirm, capture, or cancel this payment intent.

Creation of an order-owned payment intent with this idempotency key is still in progress.

Fix: Wait for the Retry-After delay, then retry the same request with the same idempotency key.

The order payment leg already settled and cannot be canceled.

Fix: Create a refund or reversal instead of canceling the payment.

The order does not have an email address that can receive a receipt.

Fix: Add an email address to the customer or order, then retry.

Flint receipt delivery is disabled because the merchant sends its own receipts.

Fix: Contact the merchant to request another receipt.

The order does not have a paid receipt that can be sent.

Fix: Check that the order has a successful payment before retrying.

A receipt was already resent for this order recently.

Fix: Wait five minutes, then retry.

The order payment state requires operational reconciliation before more money movement is safe.

Fix: Do not retry blindly. Surface support and include the request_id and order ID.

A fully refunded order cannot be closed through the normal close transition.

Fix: Read the order and preserve its refunded terminal state.

An order-scoped tax refund requires order_id.

Fix: Provide the order_id that owns the tax breakdown.

The order's current status does not allow it to be closed.

Fix: Read the order and complete the actions supported by its current status before retrying.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Partner app management requires a live API key.

Fix: Use a live management key from Dashboard, Developers, API keys.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The hosted payment attempt does not have enough remaining time to start a redirect payment.

Fix: Start a fresh order payment attempt or choose card.

A linked payment attempt currently prevents the requested order transition.

Fix: Wait for the payment attempt to finish, then read the order before retrying.

An active order payment authorization must be mutated through its owning payment attempt.

Fix: Send the payment_attempt_id returned by PayOrder or active_payment_attempt.

A payment attempt owns the resource.

Fix: Finish or cancel the owning payment attempt before changing the resource.

The submitted payment attempt does not own the selected payment intent.

Fix: Refresh the order or payment attempt, then send the owning payment_attempt_id.

The requested payment attempt cannot be resumed from its current status.

Fix: Read the attempt status and start, cancel, or capture only the work allowed by that state.

A payment-attempt resume request included fields that belong to a new start.

Fix: Send payment_attempt_id alone, with only an optional expected_outstanding_money assertion.

A previous payment attempt is still processing.

Fix: Wait briefly, then read the order and retry only after the attempt leaves processing.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The requested capture method is not allowed for this order payment caller or start shape.

Fix: Use automatic capture, or create an explicit merchant-authorized payment leg for delayed capture.

The confirmation request no longer matches the PaymentIntent's durable attempt or checkout binding.

Fix: Refresh the PaymentIntent and its owning checkout, then start a new confirmation only if the current state permits it.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The PaymentIntent does not contain a positive collectible amount and currency.

Fix: Create or update the PaymentIntent with a positive amount before starting hosted collection.

Direct hosted PaymentIntent collection does not support delayed capture.

Fix: Create the PaymentIntent with automatic capture before starting checkout.

An open hosted checkout already owns collection for this PaymentIntent.

Fix: Reuse the checkout identified by existing_checkout_session_id.

The PaymentIntent can no longer be bound to the requested checkout session.

Fix: Read the PaymentIntent and its current checkout session before creating another hosted collection flow.

A direct PaymentIntent checkout cannot change its fixed balance with checkout commerce features.

Fix: Omit tips, tax, coupons, promotions, and fulfillment from the checkout request.

A direct PaymentIntent checkout was combined with another checkout owner or replacement operation.

Fix: Send payment_intent_id as the only collection source, without invoice_id, payment_link_id, or replace_checkout_session_id.

The PaymentIntent is already owned by an Order.

Fix: Create hosted checkout with order_id so the Order remains the collection authority.

The PaymentIntent cannot accept hosted collection in its current state.

Fix: Read the PaymentIntent and start checkout only while it still permits buyer payment.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Checkout cannot override the payment options frozen on a direct PaymentIntent.

Fix: Omit payments from the checkout request. Configure payment_options on the PaymentIntent.

The PaymentIntent has no payment option available for hosted collection.

Fix: Configure at least one supported payment option on the PaymentIntent before starting checkout.

The PaymentIntent contains a payment option not supported by direct hosted collection.

Fix: Use card, Apple Pay, or Google Pay, or collect the PaymentIntent through a supported non-hosted integration.

The order payment request needs an explicit payment-leg selection.

Fix: Select the payment intents listed in the error details, create an order-owned leg, or use payment_source when no selectable leg exists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The payment link changed before the checkout publication committed.

Fix: Read the public payment link again and start a new resolve operation with a new context and idempotency key.

The payment link references delivery configuration that is not currently available.

Fix: Update the payment link to use active delivery methods, then resolve it again.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The payment-link resolution context is invalid or expired.

Fix: Read the public payment link again and start a new resolve operation with the newly issued context.

The signed context no longer has enough lifetime to start a new checkout publication safely.

Fix: Read the public payment link again and start a new resolve operation with the refreshed context.

Payment-link resolution requires a server-issued resolution context.

Fix: Read the public payment link, then send its resolution_context with the resolve request.

The client exceeded the per-link limit for public payment-link work.

Fix: Wait briefly, then retry. Reuse the same context and idempotency key unless the context expired.

The checkout recorded for this payment-link operation can no longer issue authentication.

Fix: Read the public payment link again and start a new checkout operation.

Flint could not issue or recover a payment-link resolution context.

Fix: Read the public payment link again. Contact support with the request_id if the error persists.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

Payment method domain records are temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The exact domain is already registered in this merchant environment.

Fix: Use the payment_method_domain_id returned in error.details.

The payment method domain is inactive and cannot be validated.

Fix: Activate the payment method domain, then validate it.

The payment method domain was not found in this merchant environment.

Fix: Check the payment_method_domain_id and selected environment.

Another payment method domain operation is still in progress.

Fix: Wait for the active operation to finish, then retry with the same Idempotency-Key.

The external wallet domain registration could not be updated.

Fix: Retry the same logical request with the same Idempotency-Key. Contact support with the request_id if the error persists.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

The collection context has no outstanding balance to charge.

Fix: Complete the zero-balance order without a payment source, or use setup_payment_source for an allowed future-billing setup.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

A standalone PaymentIntent requires an explicit non-empty payment_options list.

Fix: Provide at least one supported Flint payment option and retry.

The payment option has one or more readiness blockers.

Fix: Use the error details to identify every blocker, its reason, and the responsible next step.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Payment processing is temporarily unavailable for this merchant environment.

Fix: Retry with exponential backoff. Contact support with the request_id if processing remains unavailable.

The payment return destination violates Flint's clean redirect rules.

Fix: Use an absolute HTTPS URL without credentials, a query, or a fragment. Test-mode loopback URLs may use HTTP.

A redirect-capable payment option requires a clean browser return destination.

Fix: Set payment_return_url to an absolute HTTPS URL without credentials, a query, or a fragment.

The request supplied mutually exclusive payment credentials.

Fix: Keep exactly one credential field from conflicting_fields and retry.

The submitted payment source is not allowed for this caller or payment mode.

Fix: Use a payment source allowed for the authenticated caller and retry.

The saved payment method is not owned by the customer authorized for this order payment.

Fix: Use a saved payment method owned by the checkout customer, or collect a new payment source.

The payment start request does not include a payment source.

Fix: Submit payment_intents with credentials, payment_source, setup_payment_source, or a resumable payment_attempt_id.

The request supplied both a legacy payment source selection and payment options.

Fix: Remove payment_source_selection and use payment_options for the order payment.

The payment source selection did not choose a supported source.

Fix: Select the card branch in payment_source_selection and retry.

The submitted payment source is no longer available for this attempt.

Fix: Collect or select another payment source and start a new attempt.

The request mixed mutually exclusive order payment start shapes.

Fix: Keep exactly one of payment_source, payment_intents, or setup_payment_source and retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Authoritative payout allocation evidence is temporarily unavailable.

Fix: Retry after the Retry-After delay. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The payment attempt was declined or could not be completed.

Fix: Use the remediation next_actions and retry only after changing the requested payment inputs.

No authorized processing price covers this payment, so it was rejected before reaching the processor.

Fix: Contact the merchant account owner to confirm that this payment option and amount are enabled. Retrying the same request will not succeed until the account configuration changes.

Flint could not resolve the processing price for this payment. No payment was submitted to the processor.

Fix: Retry the same logical request with the same idempotency key. Contact support with the request_id if it persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The account accepted the profile update, but Flint has not finished reconciling the profile.

Fix: Retry with the same idempotency key.

Flint could not confirm the account profile update.

Fix: Retry with the same idempotency key.

Provider-backed merchant profile fields cannot be changed with a sandbox credential.

Fix: Use a live-mode credential to update support or website profile fields.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The merchant is not ready for this operation.

Fix: Complete the required merchant readiness or onboarding action before retrying.

Flint could not evaluate payment option provider readiness.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request exceeded the configured rate limit.

Fix: Retry with exponential backoff and jitter. Use the Retry-After header when present.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The connected account does not have enough available balance to issue the refund.

Fix: Restore the connected account's available balance, then retry with the same idempotency key.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The payment method's provider refund-submission window has ended.

Fix: Reimburse the customer outside the original payment method and preserve the Refund history for reconciliation.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

Reporting is temporarily unavailable.

Fix: Retry the request. Contact support with the request_id if the error persists.

The report download expired.

Fix: Create a new report for the same interval.

The report interval has not finished yet.

Fix: Use an interval_end_at at or before the current time.

The report interval exceeds the limit for its report type.

Fix: Request a shorter interval.

The report or download was not found.

Fix: Check the Flint report ID and the API key environment.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request timed out before Flint could complete it.

Fix: Retry with exponential backoff. Contact support with the request_id if the timeout persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The requested resource could not be found for the authenticated merchant and environment.

Fix: Check the resource ID, mode, and merchant context, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The requested Return action is not available in the current lifecycle state.

Fix: Read the resource's supported_actions and current blockers before choosing the next action.

The Return still has completion blockers.

Fix: Read completion_blockers, resolve each outstanding fact or effect, and retry.

The composite Return request includes a policy override that the current credential cannot authorize.

Fix: Use policy-backed decision values, or use a credential that also has commerce.returns.decisions.write.

The disposition exceeds available receipt or finalized inspection capacity.

Fix: Read the current receipt or inspection line capacity and submit an available quantity.

The Order line belongs to multiple completed Fulfillments.

Fix: Choose one of the candidate fulfillment_id values returned by the error.

The inspection exceeds current receipt-line capacity.

Fix: Read the current receipt line and inspect only its available quantity.

The Return request is structurally or semantically invalid.

Fix: Correct the fields identified by the error and retry.

The requested Return line quantity is no longer safely cancelable.

Fix: Use available_quantity and blocking_resources to cancel a smaller quantity or resolve the blocking work first.

The Return resource was not found in this merchant environment.

Fix: Check the resource ID and environment.

The PaymentIntent is not owned by the requested Return resolution.

Fix: Launch collection through the Return resolution that created the PaymentIntent.

More than one Return policy matched with the same precedence.

Fix: Change policy priority or scope so the evaluation has one deterministic winner.

The receipt verification exceeds outstanding handback capacity.

Fix: Read the Return line quantities and verify only the available quantity.

The Return resource changed before the mutation committed.

Fix: Read the current revision, reconcile the change, and retry with the current expected revision.

The proposed resolution exceeds available Return quantity or value.

Fix: Preview or read the current Return and allocate only unreserved value.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

No public API route matched the request path.

Fix: Check the path and remove unsupported trailing slashes or legacy routes before retrying.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Sandbox management requires a live API key.

Fix: Use a live management key from Dashboard, Developers, API keys.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The authenticated caller is not authorized for this operation.

Fix: Use credentials with access to the target merchant, environment, route, and scope, then retry.

The test-mode API key is not bound to a sandbox.

Fix: Create or use a sandbox-bound test key for the sandbox this request should target, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The requested scope is not available for the target API key mode.

Fix: Remove the scope or create or use a live key from Dashboard, Developers, API keys.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

A secret-bearing mutation did not provide the recovery metadata required for safe durable replay.

Fix: Do not retry blindly. Contact Flint support with the request_id.

A service required to complete the request is temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The server cannot establish a streaming response.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request could not be completed as submitted or in its current state.

Fix: Inspect the error response, correct the request or resource state, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

A tax breakdown refund is missing tax_breakdown_id.

Fix: Provide the tax_breakdown_id from the original order tax breakdown.

The selected tax breakdown is not an order-scoped additive flat tax.

Fix: Use a flat tax_breakdown_id from the original order, or refund percentage tax through its line allocation.

A tax breakdown refund is missing tax_money.

Fix: Provide tax_money for each tax breakdown being reversed.

Tax breakdown refund targets exceed the requested refund amount.

Fix: Increase amount_money or remove tax breakdown targets.

The selected payment legs cannot carry the requested tip.

Fix: Select enough tip-capable payment capacity or reduce the requested tip, then retry.

The requested tip is above the maximum allowed for the order.

Fix: Use a requested tip no greater than maximum_money, then retry.

Five reports are already pending for this merchant environment.

Fix: Wait for a pending report to finish before creating another.

The request supplied an ACH-only field without requesting ACH Direct Debit.

Fix: Remove transaction_purpose or include ach_debit in payment_options.

ACH Direct Debit requires a transaction purpose.

Fix: Set transaction_purpose to goods, services, or other and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry with the same idempotency key if this was the same logical operation.

The request includes a scope that is not in Flint's public scope catalog.

Fix: Use a canonical scope from the API key scope catalog and retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request body used an unsupported Content-Type.

Fix: Send JSON request bodies with Content-Type: application/json, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request included a query parameter this endpoint does not support.

Fix: Remove the unsupported query parameter or use a documented accepted expand encoding.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry with the same idempotency key if this was the same logical operation.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request could not be authenticated.

Fix: Send a valid Flint credential supported by this endpoint, then retry.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Flint could not complete the request because a required service or internal operation failed.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

Webhook event records are temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The webhook delivery is already being processed.

Fix: Wait for the active delivery attempt to finish, then retry the resend if needed.

Webhook delivery is temporarily unavailable.

Fix: Retry with exponential backoff. Contact support with the request_id if the error persists.

The webhook endpoint is not active.

Fix: Enable the endpoint and resolve any endpoint configuration issue before resending.

The retained webhook event payload has expired.

Fix: Use a newer webhook event. Expired payloads cannot be resent.

The environment has too many active webhook event streams.

Fix: Close an existing stream or wait for one to expire, then reconnect.

Webhook stream coordination is temporarily unavailable.

Fix: Retry with exponential backoff.

Webhook stream notifications are temporarily unavailable.

Fix: Retry with exponential backoff.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.

The request payload or query parameters did not pass validation.

Fix: Fix the field identified by the error response, then retry.