Skip to main content
Anchor to OrderCreateMandatePaymentJobResult

OrderCreateMandatePaymentJobResult

object

Requires read_payment_mandate access scope. Also: The user requires pay_orders_by_vaulted_card permission.

A job result for tracking the status of a mandate payment request on an order.

•Boolean!
non-null

This indicates if the job is still queued or has been run.

•[UserError!]!
non-null

Returns any errors that occurred during the mandate payment.

•ID!
non-null

A globally-unique ID that's returned when running an asynchronous mutation.

•Order

The order associated with the mandate payment request.

•OrderCreateMandatePaymentStatus!
non-null

The current status of the mandate payment request.


Was this section helpful?

•mutation

Creates a payment for an Order using a stored PaymentMandate. A payment mandate represents the customer's authorization to charge their payment method for deferred payments, such as pre-orders or try-before-you-buy purchases.

The mutation processes the payment asynchronously and returns a Job for tracking the payment status. You can specify the payment amount to collect, and use the autoCapture argument to either immediately capture the payment or only authorize it for later capture. Each payment request requires a unique idempotencyKey to prevent duplicate charges. Subsequent calls with the same key return the original payment result rather than creating a new payment.

Learn more about deferred payments and payment mandates and idempotent requests.

Arguments

•MoneyInput

The payment amount to collect.

•Boolean
Default:true

Whether the payment should be authorized or captured. If false, then the authorization of the payment is triggered.

•ID!
required

The ID of the order to collect the balance for.

•String!
required

A unique key to identify the payment request.

•ID!
required

The mandate ID used for payment.

•ID

The ID of the payment schedule to collect the balance for.


•mutation

Captures payment for a due PaymentSchedule using the vaulted payment method associated with the order.

The mutation resolves the order and mandate from the given payment schedule, then initiates an asynchronous payment capture. Use the returned jobResult to poll for the status of the payment capture.

Arguments

•ID!
required

The ID of the payment schedule to capture payment for.



Was this section helpful?

•interface

Was this section helpful?