{"section":"known-issues","requestedLocale":"en","requestedSlug":"transaction-stuck-on-capturing-value-sent-to-connector-yami-different-from-order-value","locale":"en","slug":"transaction-stuck-on-capturing-value-sent-to-connector-yami-different-from-order-value","path":"docs/en/known-issues/Payments/transaction-stuck-on-capturing-value-sent-to-connector-yami-different-from-order-value.md","branch":"main","content":"## Summary\n\nSome transactions with transaction split using YamiSplitV1 send a value different from the order value to the connector. When trying to capture, the payload sent has a different value than the total, typically smaller, the gateway tries to make a new capture to complete the total value, when this happens the system understands that there has already been a capture and informs that there is nothing else to be captured.\nIn some cases the gateway informs that there is nothing more to be captured.\n\n## Simulation\n\nThere is no way to replicate this behavior in a production environment.\n\n## Workaround\n\nThere is no workaround"}