Skip to main content
object

Requires read_orders access scope or read_marketplace_orders access scope.

The record of the line items and transactions that were refunded to a customer, along with restocking instructions for refunded line items.

Anchor to Fields and connectionsFields and connections

•DateTime

The date and time when the refund was created.

•[RefundDuty!]

A list of the refunded duties as part of this refund.

•ID!non-null

A globally-unique ID.

•UnsignedInt64!non-null

The ID of the corresponding resource in the REST Admin API.

•String

The optional note associated with the refund.

•Order!non-null

The order associated with the refund.

•OrderAdjustmentConnection!non-null

The order adjustments that are attached with the refund.

•RefundLineItemConnection!non-null

The RefundLineItem resources attached to the refund.

•RefundShippingLineConnection!non-null

The RefundShippingLine resources attached to the refund.

•Return

The return associated with the refund.

•StaffMember

The staff member who created the refund.

•MoneyBag!non-null

The total amount across all transactions for the refund, in shop and presentment currencies.

•OrderTransactionConnection!non-null

The transactions associated with the refund.

•DateTime!non-null

The date and time when the refund was updated.

•MoneyV2!non-nullDeprecated

Was this section helpful?

•query

Returns a Refund resource by ID.


Was this section helpful?

•mutation

Creates a refund for an order, allowing you to process returns and issue payments back to customers.

Use the refundCreate mutation to programmatically process refunds in scenarios where you need to return money to customers, such as when handling returns, processing chargebacks, or correcting order errors.

The refundCreate mutation supports various refund scenarios:

  • Refunding line items with optional restocking
  • Refunding shipping costs
  • Refunding duties and import taxes
  • Refunding additional fees
  • Processing refunds through different payment methods
  • Issuing store credit refunds (when enabled)

You can create both full and partial refunds, and optionally allow over-refunding in specific cases. The mutation also supports idempotent requests to safely retry failed refund attempts.

After creating a refund, you can track its status and details through the order's refunds field. The refund is associated with the order and can be used for reporting and reconciliation purposes.

Learn more about managing returns and refunding duties.


Note

The refunding behavior of the refundCreate mutation is similar to the refundReturn mutation. The key difference is that the refundCreate mutation lets you to specify restocking behavior for line items, whereas the returnRefund mutation focuses solely on handling the financial refund without any restocking input.


Arguments

•RefundInput!required

The input fields that are used in the mutation for creating a refund.


Fields

•Order

The order associated with the created refund.

•Refund

The created refund.

•[UserError!]!non-null

The list of errors that occurred from executing the mutation.

•mutation

Refunds a return when its status is OPEN or CLOSED and associates it with the related return request.

Arguments

•ReturnRefundInput!required

The input fields to refund a return.


Fields

•Refund

The created refund.

•[ReturnUserError!]!non-null

The list of errors that occurred from executing the mutation.


Was this section helpful?


Was this section helpful?
OSZAR »