Payment webhooks and confirmation in No-Code - Step-by-Step Execution

Concept Flow - Payment webhooks and confirmation

Payment Initiated

↓

Payment Processor Handles

↓

Webhook Sent to Merchant

↓

Merchant Receives Webhook

↓

Merchant Confirms Payment

↓

Update Order Status

↓

Notify Customer

This flow shows how a payment starts, the processor sends a webhook to the merchant, who then confirms and updates the order.

Execution Sample

No-Code

1. Customer pays on website
2. Payment processor sends webhook
3. Merchant receives webhook
4. Merchant confirms payment
5. Order status updated

This sequence shows the steps from payment to confirmation using webhooks.

Analysis Table

Step	Event	Action	Result
1	Customer completes payment	Payment processor records payment	Payment marked as pending
2	Payment processor sends webhook	Webhook sent to merchant URL	Merchant notified of payment
3	Merchant receives webhook	Merchant verifies webhook data	Payment details confirmed
4	Merchant confirms payment	Merchant updates order status	Order marked as paid
5	Merchant notifies customer	Send confirmation email or message	Customer informed of success
6	End	No further action	Process complete

💡 Process ends after customer is notified and order status updated

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Payment Status	None	Pending	Pending	Verified	Paid	Paid
Webhook Received	No	No	Yes	Yes	Yes	Yes
Order Status	Unpaid	Unpaid	Unpaid	Unpaid	Paid	Paid
Customer Notified	No	No	No	No	Yes	Yes

Key Insights - 3 Insights

Why does the merchant wait for the webhook before confirming payment?

Because the webhook is the official notification from the payment processor that payment was successful, as shown in step 3 of the execution_table.

What happens if the webhook is not received?

The merchant cannot confirm payment or update order status, so the order remains unpaid, as seen in the variable_tracker where 'Webhook Received' stays 'No'.

Why notify the customer only after updating the order status?

To ensure the customer is informed only when payment is confirmed and order is ready, matching step 5 in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the payment status after step 3?

A Verified

B Pending

C Paid

D Unpaid

💡 Hint

Check the 'Payment Status' variable in variable_tracker after step 3

At which step does the merchant update the order status to 'Paid'?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Action' column in execution_table for order status update

If the webhook is delayed, what variable remains 'No' longer according to variable_tracker?

A Payment Status

B Order Status

C Webhook Received

D Customer Notified

💡 Hint

Refer to 'Webhook Received' row in variable_tracker

Concept Snapshot

Payment webhooks notify merchants of completed payments.
Merchant waits for webhook before confirming payment.
After confirmation, order status updates to 'Paid'.
Customer is notified only after payment confirmation.
This ensures accurate and timely order processing.

Full Transcript

When a customer pays, the payment processor records the payment and sends a webhook to the merchant. The merchant waits to receive this webhook to verify the payment details. Once verified, the merchant updates the order status to paid and notifies the customer. This process ensures the merchant only confirms payments that are successfully processed, avoiding errors. The webhook acts as a trusted signal from the payment processor to the merchant's system, triggering order updates and customer notifications.