Payment links and statuses

Prodamus supports the complete payment flow: create a link for an approved purchase, send it to the customer, wait for reliable confirmation, and continue the conversation or automation based on the result.

Creating a link

The link creation tool uses only the account, items, and prices from the tool instance settings. Senler automatically supplies the project, agent, channel, conversation, and lead context; the customer does not need to provide these service values.

The application creates a unique order_id, sends it to Prodamus as the order number, and returns the payment link to the agent. The new order immediately receives pending: the link is ready, but no payment confirmation has arrived.

A technical retry with the same event identifier does not create a second order. A new intentional tool call creates a new link and a new order_id.

Confirming payment

A customer redirect to a successful payment page is not confirmation. The application changes the status only after a signed Prodamus webhook and verifies the store, order number, signature, and amount.

After confirmation, the application stores the payment and emits a payment.paid Senler event for the agent and conversation in which the link was created. The event contains the order ID, amount, currency, and order items. This becomes internal agent context and is not shown to the customer as a separate technical message.

The agent reacts only when the “Payment confirmed” event is enabled in its settings. The agent instruction determines the reply and any follow-up actions. A repeated webhook cannot produce a duplicate reaction because Prodamus and Senler use a stable event identifier.

Checking the status

The status tool returns the stored order_id, status, paid, amount, and payment link. It reads the application state and does not make a new Prodamus request on every call.

The agent must pass the order_id returned by the payment-link tool. The order must belong to the current project and conversation. The application does not select an order from conversation history automatically.

Automations

The automation editor provides “Create payment link”, “Check payment”, and “Wait for payment” steps.

A typical flow creates a link, sends it to the customer, and waits for confirmation from Prodamus. The screenshot highlights:

1. Create payment link — this step creates the order and stores the link and order_id in run variables; the following nodes send the link and check payment.

To add an action manually:

1. Select Add step to open the node catalog.
2. In the Applications group, choose the required Prodamus step: create a link, check the status, or wait for payment.

“Create payment link” is configured in the embedded Prodamus window. Select an active account and define one fixed item with its name, price, quantity, and optional description. Senler does not show its regular parameter builder for this step: the iframe configurator and builder cannot be used together.

Select the step and click Configure. The screenshot highlights:

1. Prodamus account — select the payment page where the order should be created.
2. Step result — check the variable names for order_id, the payment link, status, amount, and item code.
3. Item and fixed price — enter the product or service, name, price, quantity, and optional description.

After completing the form, save the settings with the Senler.io button outside the embedded page.

Use Step result to set run variables for order_id, payment_url, status, amount_kopecks, and item_code. Prodamus defaults each output to a same-name variable, so saving the step is usually enough. You can rename any variable in this section. Subsequent steps can use {{run.order_id}}, {{run.payment_url}}, and the other values; a standard message step can send {{run.payment_url}} to the customer.

“Check payment” and “Wait for payment” take order_id as input. If a same-name process variable exists, Senler selects it automatically; choose another variable when needed. These steps do not return order_id again: the check step returns status and paid, while the wait step returns status, paid, and optional paid_at.

“Check payment” immediately continues through Paid, Pending, or Failed. “Wait for payment” pauses the run until a signed webhook arrives and then selects a final branch. The wait cannot outlive the callback expiry shown by the platform.

An automation order is scoped to its project and lead. After copying the node to another project, configure it again and select an available Prodamus account.

Interpreting the result

Value	Meaning	Action
pending	The link exists, but no verified payment has arrived	Ask the customer to complete payment or check again later
paid: true	The signed notification and amount were verified	Continue the paid scenario

Do not treat a screenshot, customer message, or success page as proof of payment. Use only the status stored by the tool.