Commerce & payments
PayTR integration: post-payment automation from the notification URL
Connect your PayTR store with its merchant id, merchant key and merchant salt. Every successful payment reported to PayTR's notification URL starts a workflow: a thank-you message, a review request or a team alert.
- Connection type
- API key
- Scope
- Per project: every brand connects its own account
- Inbound webhook
- Yes, you get a webhook URL for incoming events
- Capabilities
- event triggers
- Setup time
- 15 min
What it does in OrqLabs
PayTR reports the result of every payment attempt to the store's notification URL. OrqLabs checks the request's hash with your merchant key and salt, replies with the plain text OK PayTR expects and, for successful payments, starts the workflow with the order number (merchant_oid), collected amount, currency, payment type and installments.
A PayTR store has one notification URL. If it's empty, you enter the OrqLabs address directly; if your site's order confirmation already uses it, you keep it and let your site's notification handler forward the same request to OrqLabs. The guide includes a PHP example.
The notification carries no buyer contact details, so the workflow looks the customer's name and phone up by order number on your site or in your sheet.
What you can automate
Post-payment thank-you
When a payment comes in, the workflow finds the customer by order number and sends a WhatsApp template or email thank-you.
Review requests
A Wait node sends an email with a review link after delivery.
Payment alerts for the team
An If node picks out large payments and alerts the team on Slack, Telegram or in the app.
Setup at a glance
Copy the merchant id, merchant key and merchant salt from the PayTR merchant panel.
In OrqLabs, go to Integrations → PayTR → Connect and fill in the three fields.
Copy the webhook address shown on the integration card.
If the notification URL is empty, enter the address under Support & Setup → Settings → Notification URL; otherwise forward the request from your site's notification handler.
Make a test-mode payment and check the workflow's runs.
Requirements
- An approved PayTR store (iFrame or Direct API).
- The merchant id, merchant key and merchant salt from the PayTR merchant panel.
- If your site already uses the notification URL, the ability to add a small forward to its handler.
What you enter when connecting
- Mağaza no *
- Merchant key *
- Merchant salt *
Good to know
- PayTR notifications contain no buyer details or line items; take them from your own record by order number.
- There is one notification URL per store; pointing the one your site uses at OrqLabs would stop your orders from being confirmed.
- Failed payments, refunds and cancellations don't start workflows.
Frequently asked questions
Why does OrqLabs reply OK to PayTR?
PayTR only treats a notification as received when the reply is the plain text OK; otherwise it sends it again. OrqLabs replies OK after the hash checks out, and never for a bad hash.
My site already receives PayTR notifications. What should I do?
Keep the notification URL as it is. Let your site's handler forward the same POST data to the OrqLabs address after doing its own work; your site keeps replying OK to PayTR.
Do test payments start workflows too?
Yes, with testMode set to true. Add an If node at the start that checks it so no live messages go out.
Get started with OrqLabs
Build your first workflow today
Start on the free plan: connect your accounts, pick a template and stay in control with approval steps. No credit card required.