Skip to main content
The smooth operation of virtual POS (Shopier, PayTR, Weepay etc.) and global Merchant of Record (Creem, Paddle) integrations on Zonely depends on the correct response of notification URLs (Webhook/Callback).

Most Frequently Asked Problems and Solutions

The confirmation notice sent by your payment organization to your site (Webhook/Callback) does not upload balance when it is received or blocked by your site.
  • 1. HTTPS Protocol Complicability: All payment providers feedback requests only because of security https:// sends via the protocol. At the beginning of defining your Callback address http:// Make sure it’s not.
  • 2. Cloudflare WAF or Bot Protection Obstacle: Cloudflare on sites that use, Cloudflare WAF, Bot Fight Mode or Under Attack Mode features to detect and manage webhook servers of the payment organization as suspicious bot HTTP 403 Forbidden can rotate.
    • Solution: Cloudflare Security → WAF → Custom Rules Go to the tab.
    • URI Path contains "/process/" Create and action the rule Bypass Save all security features as (at all)
  • 3. Accurate Callback URL Format: Webhook address for each payment method in Zonely /process/ ends with prefix:
    • Creem: https://siteniz.com/process/creem
    • Paddle: https://siteniz.com/process/paddle
    • Shopier: https://siteniz.com/process/shopier
Yes, Zonely supports MoR (Merchant of Record) Individual server owners can receive international payment without obligation to establish tax plate or company thanks to solutions (Creem and Paddle).
  • How MoR Works? Creem and Paddle pass to the seller position legally; automatically calculates VAT/VAT taxes in the country of the customer and pays to local tax apartments. It transfers your net winnings directly to your bank account or crypto wallet.
  • Creem: Turkish lira and global cards offer Apple Pay, Google Pay support.
  • Paddle: Provides you to pay with local currencies in more than 200 countries.
Mixing these two values in particularly Paddle integration is a common mistake:
  • Live API Key (pdl_live_apikey_...): Your server provides secure speech in the background with Paddle APIs. API Switchbox should be entered in the management panel.
  • Client-side Token (live_...): The user’s browser is the general key that triggers the pop-up payment window (Paddle Checkout). Client-side Token must be entered into the box.
  • When these two key locations change the payment window will not be opened or the purchase cannot be approved.