Add payment sessions to the orders app - #487
Draft
marcomontalbano wants to merge 2 commits into
Draft
Conversation
marcomontalbano
force-pushed
the
feat/662_order_app_new_payments
branch
from
August 17, 2026 10:07
8b28dab to
7196ab6
Compare
malessani
force-pushed
the
feat/more-desktop-apps
branch
from
August 20, 2026 08:56
026d955 to
9ca5353
Compare
marcomontalbano
force-pushed
the
feat/662_order_app_new_payments
branch
from
August 20, 2026 13:09
7196ab6 to
4b54c71
Compare
❌ Deploy Preview for commercelayer-dashboard-apps failed.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to commercelayer/issues-app#662
What I did
Adds support for the new payment model (API version
2026-05), where an order is funded by a list of payment sessions instead of a singlepayment_method/payment_source. Both models can coexist on an order indefinitely, so this is additive rather than a cutover.OrderPayment.tsxtoOrderPaymentLegacy.tsxand render both it and the newOrderPaymentSessionsunconditionally. Each self-gates on its own data, so only one ever shows anything for a given order.usePaymentSessionActionswith Capture and Void authorization, both behind a confirmation dialog.useResourceDetailsModalfromapp-elements, adding a payments-specific Transactions tab between Attributes and Events.payment_transactionscome back as the genericpayment_transactionstype rather thanpayment_capturesorpayment_authorizations.paymentDisplay.ts, resolving the logo, label and last 4 digits for a session, falling back from card brand to gateway to a generic credit-card icon. Card details are extracted per gateway, sinceresponse_datais verbatim gateway output with no shared shape.useOrderDetailsinclude list with the payment session relationships.@commercelayer/app-elementsacross the workspace to the preview carryinguseResourceDetailsModal.How to test
2026-05and check the Payments section lists one row per payment session.authorization succeeded,capture succeededand so on, rather than a generictransaction, and that expanding one shows its raw JSON.2017-08and check the legacy payment display is unchanged.Checklist