Add the Kushki node to your Canvas flow, configure its inputs, and test payments in the test environment.
Once connected, the Kushki node is available in Canvas and lets you create collection experiences with embedded WebView within the conversational flow.
Descriptive text for the charge. Examples: order number, product, service, or internal reference.You can map it from flow variables, for example {{$memory.paymentBreakdown.summary}}.
Defines how long the payment button remains valid after being sent.
Advanced tab of the Kushki node
Successful payment
Activates when Kushki confirms the transaction was approved.Recommendations:
confirm the order
issue a receipt or update status in external systems
Pending payment
Activates when the transaction is in process or requires later confirmation.Recommendations:
inform the user clearly
avoid creating a second charge while the status is pending
Payment message sent
Activates when the payment button message is sent successfully in the conversation.This output does not confirm payment. It only indicates the message was sent successfully.
Failed payment
Activates when the transaction was rejected, declined, or not completed.Recommendations:
allow controlled retry
offer support or an alternative path
Error
Activates on technical errors, provider errors, or communication failures.Recommendations: