Accept eligible Turkish meal cards through WooCommerce.
For e-commerce owners, developers and agencies: compatibility review, plugin or project licensing, staging installation, provider tests and production handover—subject to the merchant's provider agreement and API access.
Two purchase paths, one technical standard
Store owner
Compatibility review, plugin licence, staging installation, checkout configuration, provider test and production handover.
- Merchant/API readiness check
- WooCommerce compatibility
- Operational test checklist
Developer or agency
A project/domain licence with defined staging use, technical notes, compatibility scope and support for your client implementation.
- Implementation handoff
- Callback and order-state guidance
- Customisation scope when required
Custom integration
For a provider, checkout or business flow that cannot be handled by the current plugin package.
- API and documentation review
- Technical specification
- Build, test and maintenance boundary
Meal-card providers in Türkiye
Projects may involve providers such as MultiNet, Pluxee, Edenred/Ticket Restaurant, Setcard, MetropolCard, TokenFlex, Paye, Yemekmatik, iWallet or another Turkish meal-card programme. Brand coverage is not the same as automatic activation: the merchant must have the relevant commercial agreement, e-commerce approval and credentials/API access required by that provider.
Technical flow we verify
- The payment method appears only for the intended cart, currency and merchant configuration.
- The customer is sent through the provider's supported authorisation flow.
- The server verifies the provider response, amount and unique order reference.
- Repeated callback/webhook messages are idempotent and cannot fulfil an order twice.
- Cancellation, timeout, failed payment and browser-return differences map to safe WooCommerce states.
- Full or partial refund support is confirmed rather than assumed.
- Logs help support staff reconcile a transaction without exposing secrets or unnecessary card/customer data.
Information needed for a compatibility review
| Area | What to send | Why it matters |
|---|---|---|
| Store | URL, WooCommerce/PHP version, checkout type | Confirms the technical environment and extension conflicts to test. |
| Provider | Meal-card brand, merchant/e-commerce approval status | Determines whether a plugin test can begin or provider onboarding is still required. |
| Access | Whether test credentials and API documentation are available | Defines ready-plugin versus custom/research scope. Do not send secrets in the first message. |
| Buyer | Store owner, developer or agency; production and staging domains | Defines the correct licence and support boundary. |
| Operations | Refund, cancellation, invoice and reconciliation needs | Prevents unsupported behaviour being discovered after launch. |
Plugin price and project scope
There is no honest universal price before compatibility is known. The quote depends on provider flow, available plugin package, number of domains, staging, checkout customisation, refund support, version compatibility and installation/support requirements. You receive a written scope that separates licence, installation, custom work and ongoing support.
Frequently asked questions
Does one plugin activate every Turkish meal card?
No. Provider contracts, e-commerce permissions, credentials and technical flows differ. We check the target provider and merchant account first.
Can an agency license the plugin for a client?
Yes. Tell us the production and staging domains and the support expected. We will define a project/domain licence and implementation boundary.
Are refunds always supported?
No. Full or partial refund capability depends on the provider API and implementation. It is explicitly confirmed and tested where available.
Send the store and provider details
Share the WooCommerce URL/version, target meal-card provider, merchant/API status and whether you are the store owner or implementation partner.
WhatsApp · English available+90 534 678 99 27