Bug: Returning "capture" status from authorizePayment does not create order transactions.

[lukegreaves5]

Bug report

Describe the bug

As a developer who has implemented a custom payment provider, I want to auto capture the payment. This is supported according to the docs by setting the status to "captured" instead of authorized.

when returning the status "captured" in the authorizePayment method, the capturePayment method is called immediately as expected, but the order transactions are not being created in the database, resulting in the order summary amounts being incorrect. For example, the paid_total amount on the order is still the full order amount. See screenshots below.

System information

Medusa V2
Node.js version: v20.11.1
Database: Supabase
Operating system: MacOS Sonoma 14.4.1

Steps to reproduce the behavior

1. Using a custom payment provider, set the return status in the authorizePayment method to "captured"
2. Set the return status in the capturePayment method to "captured"
3. Place an order
4. Got to your medusa admin and find the order - see the incorrect outstanding amount and order summary values not representing the captured amount.

Expected behavior

Order summary amounts should represent the captured amount and the order transactions should be created in the database

Screenshots

[sradevski]

Thanks for the ticket, we'll have a look into it and let you know what the next steps are.

[lukegreaves5]

Thanks @sradevski. Let me know if you would like more information or even a live demo. This bug is blocking development for me and is affecting downstream operations like fulfillment and refunds.

[fPolic]

hey @lukegreaves5, a PR that we merged today should fix your issue.
I'll close this for now but feel free to reopen if the issue is still present after we release a patch.

[lukegreaves5]

Excellent. Thank you so much!