{"id":29802,"date":"2026-07-10T14:38:22","date_gmt":"2026-07-10T14:38:22","guid":{"rendered":"https:\/\/synder.com\/help\/?p=29802"},"modified":"2026-08-27T14:51:48","modified_gmt":"2026-08-27T14:51:48","slug":"when-to-sync-stripe-charges-in-synder","status":"publish","type":"post","link":"https:\/\/synder.com\/help\/when-to-sync-stripe-charges-in-synder\/","title":{"rendered":"Sync Bank-Method Transactions in Transit (Stripe)"},"content":{"rendered":"\n
This guide explains when Synder should sync Stripe charges<\/strong> that customers pay through bank methods, and it covers the Sync bank-method transactions in transit<\/strong> setting in your Stripe integration. In short, the setting controls when Synder imports ACH, SEPA, BACS<\/a>, and similar bank-debit charges \u2014 either before or after Stripe confirms their final status.<\/p>\n\n\n\n When Synder syncs Stripe charges from a bank method, the outcome depends on this setting. Here is what happens in each case.<\/p>\n\n\n\n Setting enabled (recommended):<\/strong> Synder waits for Stripe to confirm the final status before it imports the charge. As a result, your books only ever reflect money that actually cleared.<\/p>\n\n\n\n Setting disabled:<\/strong> Synder imports the charge as soon as it affects Stripe\u2019s balance. At this stage Stripe reports the charge as paid, so Synder records it as an Invoice + Payment or a Sales Receipt<\/strong>, which closes the balance.<\/p>\n\n\n\n However, if the charge later fails, Stripe sends a Payment failure refund<\/strong> that corrects the clearing account \u2014 but the invoice still remains closed. Because the invoice already has a payment attached, Synder will not sync the eventual successful payment or create an unnecessary overpayment. Consequently, this leaves Accounts Receivable in an incorrect state, since a payment that eventually failed to reach your Stripe account had already closed the invoice.<\/p>\n\n\n\n To fix this manually:<\/strong> resync the original entry that created the Invoice + Payment. Since Stripe now shows the charge as failed, Synder re-imports it as a deposit instead and removes the incorrect Invoice + Payment. Once you do that, the successful payment syncs correctly when it comes through.<\/p>\n\n\n\n With the setting on, Synder waits to sync Stripe charges from bank methods until Stripe confirms the outcome \u2014 whether succeeded<\/em> or failed<\/em>. Therefore, you should no longer see a bank-debit charge post to your books while it is still pending.<\/p>\n\n\n\n The Payment failure refund always runs, regardless of this setting.<\/strong> Whenever a Stripe charge fails, Stripe sends a reverting charge. Synder then records it as a Payment failure refund<\/strong> expense, which corrects the clearing account balance. This happens automatically, and this setting does not control it.<\/p>\n\n\n\n Existing organizations default to disabled.<\/strong> New organizations default to enabled. You can change this at any time.<\/p>\n\n\n\n This setting applies to new charges only.<\/strong> Synder does not re-evaluate already-synced charges.<\/p>\n\n\n\n Which payment methods does this affect?<\/strong> What if the setting is disabled and a charge fails?<\/strong> Does this affect charges that were already synced?<\/strong> Reach out to Synder Team<\/em><\/a> via online support chat or email with any questions you have \u2014 we are always happy to help you!<\/p>\n","protected":false},"excerpt":{"rendered":" This guide explains when Synder should sync Stripe charges that customers pay through bank methods, and it covers the Sync bank-method transactions in transit setting in your Stripe integration. In short, the setting controls when Synder imports ACH, SEPA, BACS, and similar bank-debit charges \u2014 either before or after Stripe confirms their final status. How […]<\/p>\n","protected":false},"author":2320,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","footnotes":"","_ppma_block_editor_authors":""},"categories":[2,360,438,437],"tags":[],"ppma_author":[471],"class_list":["post-29802","post","type-post","status-publish","format-standard","hentry","category-get-started","category-configure-core-settings","category-stripe-payment-integration","category-payment-integrations-main"],"yoast_head":"\n\n
How to enable the setting<\/strong><\/h2>\n\n\n\n
\n
What happens when you sync Stripe charges<\/strong><\/h2>\n\n\n\n
\n
How to confirm it worked<\/strong><\/h2>\n\n\n\n
Limitations and important notes<\/strong><\/h2>\n\n\n\n
FAQ<\/strong><\/h2>\n\n\n\n
<\/strong>It affects ACH, SEPA, BACS, ACSS debit, and similar bank-debit methods. Card payments, on the other hand, are unaffected.<\/p>\n\n\n\n
<\/strong>In that case, resync the original entry in Synder. Since Stripe now shows the charge as failed, Synder re-imports it as a deposit instead of an Invoice + Payment. This then clears the way for the successful payment to sync correctly when it arrives.<\/p>\n\n\n\n
<\/strong>No. The setting only applies to new incoming charges.<\/p>\n\n\n\n