SHINRO

Workflows

Continue after the payment.

Start one durable chain from the terminal payment state, run live PDF and Webhook steps, and inspect every result in its trace.

Get early accessExplore routing
Execution trace preview
acme.shinro.app/workflows/runs/run_demo

Durable steps

Resume from the last completed step.

DBOS checkpoints the chain after the payment reaches a terminal state and keeps one run per payment with its trace.

  • A run id gives retries an exactly-once workflow identity.
  • Completed steps survive a restart and recovery continues from the next checkpoint.
  • Step audits are hash-chained so the run history can be verified.

Steps (3)

1Generate PDFChainSUCCEEDED97ms
Document numberRE-2026-0042
FormatFactur-X
2WebhookChainSUCCEEDED121ms
Endpoint/v1/orders/paid
HTTP status200 OK
3NotifyChainPENDING8ms
ChannelEmail
DeliveryQueued

PDF step

Generate the document inside the chain.

The live PDF executor sends payment context to a selected template and records the document result on the run.

  • Use free-form, Factur-X, or XRechnung templates.
  • A deterministic document id prevents the same run step from creating duplicates.
  • The next success or failure edge follows the executor outcome.

Muster Handels GmbH

Beispielstraße 12
10115 Berlin
DE123456789

Invoice

RE-2026-0042

Buyer

Erika Mustermann

Musterweg 3
80331 München
DE

Issue date
12.07.2026
Due date
26.07.2026
Reference
RE-2026-0042
DescriptionQuantityUnit priceAmount
Beratungsleistung Konzeptphase10 HUR120,001.200,00
UI/UX-Designpaket1 C62850,00850,00
Softwarelizenz (Jahresabonnement)3 C6249,00147,00
Net
2.197,00 EUR
VAT 19 %
417,43 EUR
Total
2.614,43 EUR

Webhook step

Send the outcome to the system that needs it.

The live Webhook executor posts payment and run context to the configured HTTPS endpoint.

  • The payload includes payment status, amount, currency, workflow, run, and node identifiers.
  • Retryable delivery outcomes are retried by the durable step.
  • Encrypted request and response snapshots remain attached to the trace.

Webhook delivery

Request status200 OK
Endpointhttps://erp.acme.de/payments
Retries0 / 3
Payload keyspayment.statuspayment.amountpayment.currencyrun.id

Product areas

Keep the rest of the payment in one flow.

Routing

Readable rules for every attempt.

Control provider order, handoff policy, and smart routing from one visual workflow.

Explore this area

Checkout

A hosted path into the route.

Shape payment methods, fields, and merchant tokens in the checkout builder.

Explore this area

E-invoicing

Documents from the final payment state.

Generate validated Factur-X and XRechnung documents inside the payment flow.

Explore this area

FAQ

Questions merchants ask first.

Clear answers about payment orchestration, provider control, and pricing.

A workflow can react to the final payment state and trigger downstream steps such as invoice generation or webhooks.

Early access

Get early access.

Tell us about your setup and we will get in touch.