Connector Contracts - Create Order Payment
Changed on:
13 Dec 2023
Overview
Payment transactions reflect when and how a customer has paid for an . Multiple (split) payments are supported and custom business logic can be applied on the Fluent side, to identify when an has been fully paid.
Considerations for the payment :
- The workflow needs to reflect the business model on when to capture the payment: at order placement, or at fulfilment.
- Create order payment should simply track the payment details against the order placed, nothing more.
- All available payment transactions (authorisation and/or capture) should be pushed to Fluent.
- These transactions can be used to issue refunds on returns or cancellations.
- Payment pre-authorisations usually only hold for 5-7 days. The workflow should expect it to fail when capturing at fulfilment time for delayed orders.
- Pre-orders will need a different flow, as capturing at fulfilment time will most likely be outside the 5-7 window.
API Details
Event Names
`fc.connect.order.transaction.add`
API contract
To download the add payment transaction payload schema click here.
Interface Contract
Diagram

Configuration example
1Not available
Request Payload
Property | Description | Type | Required? | Notes |
Version History
v0.0.0
First release