The flow
Starts it 10Logic 6Service 2
The steps in the order they run, from what starts it.
- 1/verifyWebhookStarts it
- 2/settleWebhookStarts it
- 3/supportedWebhookStarts it
- 4Check POST PayloadIfLogic
- 5Supported Networks ConfigCodeLogic
- 6Lookup Payment Configs & Split SignatureCodeLogic
- 7Bad PayloadIfLogic
- 8Response: Return Supported NetworksRespond To WebhookStarts it
- 9verify or settleIfLogic
- 10Unsupported TokenIfLogic
- 11Response: Bad POST Body (/verify)Respond To WebhookStarts it
- 12Response: Bad POST Body (/settle)Respond To WebhookStarts it
- 13Simulate PaymentOne ShotService
- 141Shot API Submit & WaitOne Shot SynchService
- 15Response: Unsupported Token (/verify)Respond To WebhookStarts it
- 16Response: Unsupported Token (/settle)Respond To WebhookStarts it
- 17Verify ResponseRespond To WebhookStarts it
- 18Settlement ResponseRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 18, with 4 branches
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 18 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 18 steps before you point it at anything that matters.