{"section":"known-issues","requestedLocale":"en","requestedSlug":"payment-created-without-connector-leads-to-canceled-transaction","locale":"en","slug":"payment-created-without-connector-leads-to-canceled-transaction","path":"docs/en/known-issues/Payments/payment-created-without-connector-leads-to-canceled-transaction.md","branch":"main","content":"## Summary\n\n\nIn some checkout flows, the payment fails because the required `connector` field is not included in the `/payment` payload. As a result, the payment is created without an assigned connector, which prevents it from being properly processed by the provider. This issue usually occurs when the Payments API is called programmatically without setting the `connector` field or when no rule or affiliation is correctly bound before the provider handoff.\n\n\n#### Simulation\n\n\nIt is not possible to simulate.\n\n\n#### Workaround\n\n\nN/A."}