Skip to main content
object

The schema's entry point for all mutation operations.

Anchor to captureSessionRejectcaptureSessionReject
•CaptureSessionRejectPayload

Rejects an open capture session.

After the captureSessionReject mutation completes on a given capture session, any captureSessionResolve mutation attempts will fail. Subsequent captureSessionReject mutation attempts will succeed, but the reason argument will be ignored.

Anchor to captureSessionResolvecaptureSessionResolve
•CaptureSessionResolvePayload

Resolves an open capture session.

After the captureSessionResolve mutation completes on a given capture session, any captureSessionReject mutation attempts will fail. Subsequent captureSessionResolve mutation attempts will succeed.

Anchor to paymentsAppConfigurepaymentsAppConfigure
•PaymentsAppConfigurePayload

Configures the partner-managed payments gateway to work on the merchant's store. For an example of how to use the paymentsAppConfigure mutation, refer to the tutorial for onboarding merchants to payments extensions.

Anchor to paymentSessionConfirmpaymentSessionConfirm
•PaymentSessionConfirmPayload

Initiates the confirmation process of the given payment_session.

Shopify will start confirming the payment. According to its business logic, Shopify determines if the payment can be authorized and sends a POST request to the payments app, delivering the confirmation result.

•PaymentSessionModalPayload

Raises a modal that will be displayed to the buyer after a checkout is completed. Included data will be used to populate the UI extension in the modal.

Anchor to paymentSessionPendingpaymentSessionPending
•PaymentSessionPendingPayload

Change a payment session status to pending.

Upon receiving the response from the PaymentSessionPending mutation, you must redirect the customer back to Shopify, using redirectUrl in nextAction.

Upon completion, pending payments must be finalized into either a successful or failed state using the paymentSessionResolve or paymentSessionReject mutations. Both sale and authorization payments can be marked as pending.

Anchor to paymentSessionRedirectpaymentSessionRedirect
•PaymentSessionRedirectPayload

Redirects the buyer to the given URL for the payment session. For example, Shopify will redirect the buyer to the URL where the 3DS authentication will take place for onsite payment with credit_card payment method.

Anchor to paymentSessionRejectpaymentSessionReject
•PaymentSessionRejectPayload

Rejects an open payment session. After the paymentSessionReject mutation completes on a given payment session, any paymentSessionResolve mutation attempts will fail. Subsequent paymentSessionReject mutation attempts will succeed, but the RejectionReasonInput argument will be ignored.

Anchor to paymentSessionResolvepaymentSessionResolve
•PaymentSessionResolvePayload

Resolves an open payment session. After the paymentSessionResolve mutation completes on a given payment session, any paymentSessionReject mutation attempts will fail. Subsequent paymentSessionResolve mutation attempts will succeed, but the Details argument will be ignored.

•RefundSessionRejectPayload

Rejects an open refund session. After the refundSessionReject mutation completes on a given refund session, any refundSessionResolve mutation attempts will fail. Subsequent refundSessionReject mutation attempts will succeed, but the RejectionReasonInput argument will be ignored.

Anchor to refundSessionResolverefundSessionResolve
•RefundSessionResolvePayload

Resolves an open refund session. After the refundSessionResolve mutation completes on a given refund session, any refundSessionReject mutation attempts will fail. Subsequent refundSessionResolve mutation attempts will succeed, but the Details argument will be ignored.

Anchor to verificationSessionRedirectverificationSessionRedirect
•VerificationSessionRedirectPayload

Redirects the buyer to the given URL for the verification session. Shopify will redirect the buyer to the URL where the 3DS authentication will take place when verifying the buyer's credit_card.

Anchor to verificationSessionRejectverificationSessionReject
•VerificationSessionRejectPayload

Rejects an open verification session. After the verificationSessionReject mutation completes on a given verification session, any verificationSessionResolve mutation attempts will fail. Subsequent verificationSessionReject mutation attempts will succeed, but the RejectionReasonInput argument will be ignored.

Anchor to verificationSessionResolveverificationSessionResolve
•VerificationSessionResolvePayload

Resolves an open verification session. After the verificationSessionResolve mutation completes on a given verification session, any verificationSessionReject mutation attempts will fail. Subsequent verificationSessionResolve mutation attempts will succeed, but the Details argument will be ignored.

•VoidSessionRejectPayload

Rejects an open void session. After the voidSessionReject mutation completes on a given void session, any voidSessionResolve mutation attempts will fail. Subsequent voidSessionReject mutation attempts will succeed, but the RejectionReasonInput argument will be ignored.

•VoidSessionResolvePayload

Resolves an open void session. After the voidSessionResolve mutation completes on a given void session, any voidSessionReject mutation attempts will fail. Subsequent voidSessionResolve mutation attempts will succeed, but the Details argument will be ignored.


Was this section helpful?