Zapier
seQura for Zapier
Connect seQura payments to your favorite apps. Create payments and send checkout links to shoppers, all from your Zaps.
Table of Contents
Getting Started
What You Need
- A Zapier account
- Your seQura API credentials (account key and secret) from the seQura Merchant Portal
Connect Your Account
Add seQura to a Zap and you'll be asked for 3 things:
| Field | What it is |
|---|---|
| Environment | Where to connect. Pick Sandbox to test, Live for real payments. |
| Account Key | Your API username. It doubles as your Merchant ID. |
| Account Secret | Your API password. |
Both credentials are in the Merchant Portal.
These are the available environments:
| Environment | When to use |
|---|---|
| Live seQura | Real payments (seQura) |
| Live SVEA | Real payments (SVEA) |
| Sandbox seQura | Testing (seQura) |
| Sandbox SVEA | Testing (SVEA) |
Start with Sandbox to try things out. Switch to Live when you're ready.
Available Actions
Create Payment
Create a seQura payment and send the checkout link to the shopper via SMS, email, or grab it yourself.
Input fields
| Field | Required | Default | What it does |
|---|---|---|---|
| Channel | Yes | — | How the shopper gets the checkout link: SMS, Email, or No delivery (you share it yourself). |
| Shopper Email | Yes | — | Shopper's email. |
| Shopper Phone | Only for SMS | — | Shopper's phone. Required when channel is SMS. |
| Shopper Given Names | No | — | Shopper's first name(s). |
| Shopper Surnames | No | — | Shopper's last name(s). |
| Total Amount (cents) | Yes | — | Total in cents. 12345 = 123.45 EUR. |
| Currency | No | EUR | ISO 4217 currency code. |
| Payment Method / Product | No | Any available | The seQura product to use. Options load from your account. Leave as "Any available" and seQura picks the best fit. |
| Reference | No | — | Your own reference for this payment (e.g., order ID). |
| Item Names | No | — | Line item names, one per entry. |
| Item Quantities | No | 1 | Quantity per item, same order as names. Defaults to 1. |
| Item Unit Prices (cents) | No | — | Unit price in cents per item, same order as names. |
| Notification URL | No | — | Webhook URL for payment status updates (IPN). |
| Test Mode | No | false | Set to true for a test payment. Nothing gets charged. |
Output fields
Use these values in the next steps of your Zap:
| Field | What you get |
|---|---|
| uuid | Unique ID of the payment. |
| payment_url | Full API URL for the payment. |
| payment_link | Checkout link to share with the shopper or embed in your app. |
Line items
Add items by filling in Item Names, Item Quantities, and Item Unit Prices. They work as parallel lists -- first entry matches first item, second matches second, and so on.
Example:
| Item Names | Item Quantities | Item Unit Prices (cents) |
|---|---|---|
| T-Shirt | 2 | 1500 |
| Jeans | 1 | 4999 |
Result: 2x T-Shirt at 15.00 EUR each, 1x Jeans at 49.99 EUR.
Common Zap Examples
Send a checkout link when a deal closes
- Trigger: CRM deal hits "Closed Won" (HubSpot, Salesforce, Pipedrive...)
- Action: seQura - Create Payment (channel: Email)
- Action: Save the payment link and UUID back to the CRM
Collect payment from a form submission
- Trigger: New form entry (Google Forms, Typeform, JotForm...)
- Action: seQura - Create Payment (channel: SMS or Email)
- Action: Notify your team via Slack or email
Track payment status with webhooks
- Trigger: Webhooks by Zapier (Catch Hook) -- use this URL as the Notification URL in Create Payment
- Action: Filter by payment status
- Action: Update your database, CRM, or ping your team
Troubleshooting
"Invalid email format"
Check the shopper email looks right (e.g., [email protected]). Extra spaces or odd characters will cause this.
"Phone number is required when channel is SMS"
SMS needs a phone number. Make sure the field is mapped and not empty.
"Authentication failed"
- Double-check your Account Key and Account Secret. Watch out for extra spaces.
- Confirm you picked the right Environment for your credentials (Sandbox vs. Live).
"No Location header in response"
Something went wrong on seQura's side. Check your request data and try again. If it keeps happening, reach out to seQura support.
Payment created but shopper didn't get the link
- SMS: Make sure the phone number includes the country code.
- Email: Ask the shopper to check their spam folder.
- No delivery: seQura won't send anything with this option. Share the
payment_linkfrom the output yourself.
Updated 3 days ago