Libyan Payments for MyPay

Libyan Payments for MyPay connects your store to the MyPay payment platform (mypay.ly) so you can accept secure local payments across Libya.

This plugin allows merchants to accept payments directly on their WooCommerce store using Libya’s local payment methods, including bank cards, Edfali, Sadad, Mobicash, Yaser Pay, Sahara Pay, Masrafi Pay, and optional prepaid card when enabled for your merchant in MyPay. Orders are confirmed using a signed webhook, not by relying on the customer’s browser return alone.

Key features

• Seamless integration with WooCommerce and WooCommerce Blocks checkout
• Secure payment processing through MyPay hosted checkout
• Customizable payment gateway title and description
• Signed webhook verification using X-MyPay-Signature
• Alias gateways for supported MyPay payment methods
• Logging for troubleshooting

Requirements

• WordPress 6.5 or newer
• WooCommerce (from WordPress.org)
• PHP 7.4 or newer
• A MyPay merchant account with API credentials

Configuration

1. Go to WooCommerce -> Settings -> Payments.
2. Click on “MyPay” to configure the gateway.
3. Enable the gateway by checking the “Enable MyPay Gateway” box.
4. Enter your MyPay Client ID and Secret ID from your MyPay merchant dashboard.
5. Use the environment switch:
   • Production = unchecked, which targets /pay/api/v1
   • Sandbox = checked, which targets /pay/sandbox/api/v1
6. Paste the Webhook Secret from your MyPay merchant dashboard.
7. Keep the generated Webhook URL configured in your MyPay merchant API settings.
8. Customize the title and description if desired.
9. Save changes.

External services

This plugin connects to MyPay (https://mypay.ly) to process payments and synchronize merchant connection status when API credentials are configured. MyPay is required for checkout and order confirmation.

What is sent and when

• Payment API (/authentication/token, /payment/create): order amount, currency, billing name, email, phone, order ID, return/cancel/webhook URLs, and selected gateway alias when a customer pays.
• Webhook (incoming to your site): signed payment status payload from MyPay to finalize WooCommerce orders.
• Connection sync (/plugin/connect, /plugin/disconnect, /plugin/heartbeat): site URL, plugin/WP/WC versions, environment (production/sandbox), enabled gateway flags, and plugin active state when you save MyPay credentials or change gateway settings. This supports merchant setup verification on MyPay.
• Optional health telemetry (/plugin/telemetry-consent): only when you explicitly enable “Share optional plugin health data with MyPay” in gateway settings (disabled by default). No customer, order checkout payload, or admin personal data is included.

This service is provided by MyPay:

• Terms of Service: https://mypay.ly/page/terms-and-conditions
• Privacy Policy: https://mypay.ly/page/privacy-policy

Production notes

• The plugin uses an embedded MyPay host and only needs the environment switch.
• The webhook secret in WooCommerce must match the webhook secret configured for the merchant key in MyPay.
• Alias gateways such as yasr-pay, masrafi-pay, sahary-pay (shown in the store as Sahara Pay), moamalat (shown as Banking Card), edfali, sadad, and mobicash must also exist and be enabled in the merchant gateway settings on MyPay.
• The prepaid-card alias requires prepaid card payments to be enabled for your merchant in MyPay.
• A customer returning from MyPay does not complete the WooCommerce order by itself; the signed webhook is the source of truth for final order completion.

Privacy & tracking

• Payment processing requires MyPay API calls once credentials are saved (Software as a Service).
• Operational connection sync is sent when credentials are configured to support merchant setup on MyPay.
• Optional plugin health telemetry is disabled by default and can be enabled in WooCommerce -> Settings -> Payments -> MyPay.
• No customer checkout payload or admin personal data is sent as part of optional plugin health metadata.

Credits

Developed by MyPay – https://mypay.ly