Hi there, I cancelled the refunded an order with id=“gid://shopify/Order/6002887098545” mutation($orderId: ID!) { orderCancel( orderId: $orderId restock: true reason: OTHER refund: true ) { job { id done } orderCancelUserErrors { code field …

Hey @sengming , I realized we overlooked a mutation that might actually simplify this whole process for you! The markOrderAsPaid mutation works great for orders created with orderCreate. Here’s how it functions: you create your order with financialStatus: "PENDING" (no transactions needed), then use…

Hey @sengming , I’ve taken a look at the other thread. To confirm if this is the same behavior, can you tell me how this order was originally processed? When you look at the order timeline, do you see the refund being processed on the order as a result of the mutation? If you don’t have access to t…

Hey @sengming , Are you still experiencing this issue, or can I mark this as solved?

Hi @KyleG-Shopify no this is still an issue do not mark it as solved. I just got back from vacation and I’ll be replying to your previous mail soon.

hi @KyleG-Shopify the order was created with Order - REST here are the order events {"order" => {"events" => {"edges" => [{"node" => {"__typename" => "BasicEvent", "id" => "gid://shopify/BasicEvent/135745925087409", "action" => "placed", "message"…

Hi there, are the any updates on this? Thanks!

Hey @sengming , I was able to replicate what you’re seeing and dug into the other thread that Alan was investigating. What I see here matches with what was already reported by Alan. What I found is that this is currently working as intended. When an order is marked as “PAID” but hasn’t actually pro…

thanks for looking into this! I’m glad that y’all are looking into it. One more thing, can you confirm that orders created with graphql, e.g. with orderCreate - GraphQL Admin will not be affected by this?

It’s not just for REST. I tested the orderCreate GraphQL mutation as well and it exhibits exactly the same behavior. The issue occurs when orders are created with financialStatus: "PAID" but don’t have associated payment transactions. Here’s what I found across different creation methods: Orde…

Order financial_status still paid after order is cancelled and refunded

GraphQL Admin API Troubleshooting

sengming July 16, 2025, 6:48pm 2

this might be related to Order financial status is still 'paid' after order is cancelled which is still unresolved.

Topic		Replies	Views
Order financial status is still 'paid' after order is cancelled Products and Orders APIs admin-api-orders	19	427	July 24, 2025
Order Financial Status Not Updated After Successful Refund via Amazon Payment Services Products and Orders APIs admin-api-orders	1	70	June 30, 2025
Order cancellation now supports refunds to store credit Changelog	0	53	July 1, 2025
Bug? - OrderCancel mutation sends email to customer before updating order status GraphQL Admin API Troubleshooting general-gql-troubles	4	71	January 23, 2026
Updating Order Status to "Paid" via Mutation GraphQL Admin API Troubleshooting general-gql-troubles	8	255	August 23, 2025

Order financial_status still paid after order is cancelled and refunded

Related topics