Many customers’ downstream systems (ERPs, fulfilment hubs, reporting tools, etc.) need the Stripe CaptureRequestId to reconcile payments.
This artfcle introduces:
-
Database support – a CaptureRequestId column is present on the Transaction table.
-
Connect: Flow “Payment” node – an optional block of detailed payment data (including CaptureRequestId) that can be added to every MIS.Generic XML/JSON payload.
-
A new settings group – lets you turn the Payment node on or off globally and/or per supplier.
Key settings
| Setting |
Location |
What it does |
| Include payment information |
Admin âžś Configuration âžś Plugins âžś Connect: Flow [Configure] |
When ON, the connector injects the full <Payment> node into the payload. When OFF, no payment data is sent (default for backwards-compatibility). |
| General vs. Supplier-specific toggle |
Admin âžś Configuration âžś Plugins âžś Connect: Flow [Configure] âžś Suppliers [Tab] |
Lets you override the global choice for a specific supplier if they do (or don’t) require the extra data. |
Fields inside the <Payment> node
PaymentMethod
PaymentTransactionId
CaptureTransactionId
PurchaseOrderNumber
InfigoTransactionId
AuthorizationRequestId
CaptureRequestId ← new & critical
CurrencyCode
Amount
AuthorizationExpirationDateUtc
TransactionDateUtc
Typical use cases
| Use case |
Why the Payment node helps |
| ERP reconciliation |
Finance teams can match Stripe captures to sales orders by CaptureRequestId. |
| Chargeback investigations |
Support agents see full transaction lineage (auth → capture IDs) inside their MIS logs. |
| Multi-capture orders |
Future-proofed: the <Payment> node is already a list, so multiple transactions per order won’t break existing integrations. |
| |
|
Step-by-step implementation guide
1 Enable the Payment node
-
Sign in as an administrator.
-
Navigate to Admin âžś Configuration âžś Plugins âžś Connect: Flow [Configure]
-
Toggle “Include payment information” to ON.
-
Save your changes.
3 Verify the payload
-
Place a test order on a storefront that uses ExternalPayments.
-
Allow the Connect Flow job to post to your test API endpoint
-
Confirm the <Payment> node is present and contains the fields listed above, including a non-null <CaptureRequestId>.