Create Stripe payment links and subscription links from reviewed Sanka orders and subscriptions.
Last updated: May 29, 2026
This guide explains how to create Stripe payment links from Sanka orders and subscription records. Use it after Stripe is connected and your team has reviewed the order, subscription, customer, amount, currency, line items, and link storage field.For the full Stripe import and reconciliation setup, see Sanka for Stripe setup.
What the action supports
Use Stripe payment-link actions when you want a customer to pay through Stripe while Sanka keeps the business record, source order or subscription, and action history available for review.Depending on your workspace setup, the action can help with:
Creating a Stripe payment link from a Sanka order
Creating a Stripe subscription link from a Sanka subscription
Saving the generated link back to a selected Sanka field
Including optional shipping or postal-code information when your workflow requires it
Reviewing action history before sending the link to a customer
Creating a Stripe link does not automatically mean the customer has paid. Confirm payment status, imported Stripe invoices or payments, and Sanka payment allocation separately.
Sample prompt
/sanka Review this Stripe link request before creating or sending anything. Confirm the Stripe integration, order or subscription, customer, amount, currency, line items, shipping details if used, field that will store the link, and how payment status will be confirmed afterward. Do not create or send the link until I approve the plan.
Prerequisites
Stripe is connected in Sanka.
The order or subscription exists in Sanka.
The selected record includes the amount, currency, customer, and line item information needed for payment.
The order or subscription has a field where the generated Stripe link can be saved if your workflow needs to store it.
Your team has decided who reviews the link before it is sent to the customer.
Create a payment link from an order
In Sanka, open the workflow or action setup used by your team.
Choose a manual trigger or the trigger your team uses for payment-link review.
Select the Stripe payment-link action for orders.
Choose the connected Stripe integration.
Select the Sanka order.
Select the field where the Stripe payment link should be saved.
If shipping information is required, select the postal-code and shipping-fee fields used by your workflow.
Save and run the action only after reviewing the order.
Create a subscription link
In Sanka, open the workflow or action setup used by your team.
Choose a manual trigger or the trigger your team uses for subscription-link review.
Select the Stripe payment-link action for subscriptions.
Choose the connected Stripe integration.
Select the Sanka subscription.
Select the field where the Stripe subscription link should be saved.
Save and run the action only after reviewing the subscription amount, billing interval, customer, and line items.
Expected output
After the action succeeds, review the output before sending anything to a customer.Expected results include:
A Sanka record URL for the source order or subscription
A Stripe payment or subscription URL
The generated link saved to the selected Sanka field, if configured
Action history showing who or what generated the link and when
Troubleshooting
The link was not generated
Confirm that Stripe is connected, the selected order or subscription exists, and the record includes customer, amount, currency, and line item details. Then review the action history for the specific failure.
The link is not saved on the record
Confirm the selected field exists on the order or subscription and accepts a URL or text value. If the field was renamed or removed, update the action configuration before rerunning it.
Tax, shipping, or total amount is wrong
Review the order or subscription line items, currency, tax settings, postal-code field, and shipping-fee field. Do not send the link until the amount shown in Stripe matches the amount your team expects.
The customer says they paid but Sanka is not updated
Creating a link and receiving payment are separate steps. Check Stripe payment status, then review Stripe invoice/payment import, Sanka payment records, and invoice or order allocation rules.
A link was sent to the wrong customer
Review the action history, source record, customer, recipient field, and message history. Revoke or replace the link in Stripe if needed, then correct the Sanka record before sending a new link.
Checkpoints
Use Sanka orders, subscriptions, payment records, action history, workflow history, message history, and audit logs to confirm the Stripe link flow before replying to a customer or asking AI to make a code change.
Search Sanka...
Review Stripe payment-link activity
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Reviewed Stripe link request2026/05/10 18:00Order SO-4001Checked customer, amount, currency, line items, and link fieldClaude integration
2Created Stripe payment link2026/05/10 18:10Order SO-4001Generated payment link and saved it to the orderSanka action
1Checked payment status2026/05/10 18:30Stripe paymentConfirmed payment status before updating Sanka payment allocationSanka user
A safe review should include the source order or subscription, Stripe integration, customer, amount, currency, generated link, send history, payment status, and any downstream payment allocation.
Expected results include:
