Umbraco Forms payment workflow in headless setup

bjarnef · January 5, 2026, 8:18am

I wonder if any has used payment integration with Umbraco Forms, e.g. QuickPay, in a headless setup?

In traditional MVC project using Umbraco Forms workflow, we can have a redirect as in eMerchantPay example here:

github.com/umbraco/Umbraco.Forms.Integrations

src/Umbraco.Forms.Integrations.Commerce.EMerchantPay/PaymentProviderWorkflow.cs

main-v10


      
              var createPaymentTask = Task.Run(async () => await _paymentService.Create(payment));
          
              var createPaymentResult = createPaymentTask.Result;
          
              if (createPaymentResult.Status != "error")
              {
                  // add unique ID and status to record
                  formHelper.UpdateRecordFieldValue(uniqueIdKey, createPaymentResult.UniqueId);
                  formHelper.UpdateRecordFieldValue(statusKey, createPaymentResult.Status);
          
                  _httpContextAccessor.HttpContext.Items[Core.Constants.ItemKeys.RedirectAfterFormSubmitUrl] = createPaymentResult.RedirectUrl;
          
                  return WorkflowExecutionStatus.Completed;
              }
          
              formHelper.UpdateRecordFieldValue(statusKey, "error");
          
              _logger.LogError($"Failed to create payment: {createPaymentResult.TechnicalMessage}.");
          
              return WorkflowExecutionStatus.Failed;
          }

We could probably have an API controller without workflow to generate payment link, but it may be ideal to use workflow to register payment on record initially to updated after callback.

Maybe execute workflow and an a API request after submission with a short delay to ensure workflow has executed.

bjarnef · January 9, 2026, 1:39pm

@rickbutterfield is it possible via workflow to return data after submitted, when the workflow trigger on submit?

I can set data on record e.g. based on hidden field in form, but after submission via Delivery API it only returns 200 OK:

mistyn8 · January 9, 2026, 3:42pm

Would you just take this out of the process thread? eg the forms workflow just generates a payment pending.

Then hangfire/some other process in another thread then polls for payment pendings having been completed and does whatever else needs to happen, order confirm email etc?

Never been a fan of workflows that redirect, as what if multiple are added, which one wins? And always confuses clients who have set a redirect to thank you page..

Also modern browsers won’t let you redirect via js unless it’s actioned by the end user..