Ezone Pay creates payment-link checkout sessions from WordPress. The plugin stores a local payment reference, displays the returned payment link in an iframe, and updates payment status by polling the Ezone Pay API after the customer returns to WordPress.<\/p>\n\n
Features:<\/p>\n\n
Important: embedded checkout depends on Ezone Pay allowing your site domain in iframe\/frame headers. If the Ezone Pay checkout page blocks framing, Ezone Pay must allow the merchant site domain or the browser will block the iframe.<\/p>\n\n
The plugin supports two API modes:<\/p>\n\n
https:\/\/test.ezonepay.ly<\/code><\/li>\n- Production:
https:\/\/api.ezonepay.ly<\/code><\/li>\n<\/ul>\n\nTo get a development API key, register or log in at https:\/\/demo.ezonepay.ly\/<\/code>, then go to \u0627\u0644\u0625\u0639\u062f\u0627\u062f\u0627\u062a > \u0645\u0641\u0627\u062a\u064a\u062d API<\/strong>.<\/p>\n\nTo get a production API key, register or log in at https:\/\/my.ezonepay.ly\/<\/code>, then go to \u0627\u0644\u0625\u0639\u062f\u0627\u062f\u0627\u062a > \u0645\u0641\u0627\u062a\u064a\u062d API<\/strong>.<\/p>\n\nWhen creating an API key, enable these permissions:<\/p>\n\n
\n- \u0625\u0646\u0634\u0627\u0621 \u0631\u0627\u0628\u0637 \u062f\u0641\u0639<\/strong><\/li>\n
- \u0639\u0631\u0636 \u0631\u0648\u0627\u0628\u0637 \u0627\u0644\u062f\u0641\u0639<\/strong><\/li>\n<\/ul>\n\n
You can manage settings in WordPress admin or define constants in wp-config.php<\/code>:<\/p>\n\ndefine('EZONE_PAY_API_MODE', 'dev');\ndefine('EZONE_PAY_DEV_API_KEY', 'your-dev-secret-key');\ndefine('EZONE_PAY_PRODUCTION_API_KEY', 'your-production-secret-key');\n<\/code><\/pre>\n\nIf your WordPress server cannot resolve one of the default API hosts, you can override the base URL:<\/p>\n\n
define('EZONE_PAY_DEV_BASE_URL', 'https:\/\/test.ezonepay.ly');\ndefine('EZONE_PAY_PRODUCTION_BASE_URL', 'https:\/\/api.ezonepay.ly');<h3>Shortcode<\/h3>\n<\/code><\/pre>\n\nUse:<\/p>\n\n
[ezone_pay_button amount=\"0.1\" reference=\"ORDER-123\" title=\"Pay with Ezone\"]\n<\/code><\/pre>\n\nOptional customer fields:<\/p>\n\n
[ezone_pay_button amount=\"0.1\" reference=\"ORDER-123\" title=\"Pay with Ezone\" customer_first_name=\"Ali\" customer_last_name=\"Saleh\" customer_phone=\"0910000000\"]\n<\/code><\/pre>\n\nEzone Pay requires customer data when creating a payment link. If the shortcode does not include customer details, the plugin sends WordPress Guest<\/code> and 0910000000<\/code>.<\/p>\n\nCustomer data<\/h3>\n\n
The plugin sends customer data to Ezone Pay in this shape:<\/p>\n\n
Customer.FirstName\nCustomer.LastName\nCustomer.PhoneNumber\n<\/code><\/pre>\n\nCustomer values can come from shortcode attributes:<\/p>\n\n
[ezone_pay_button amount=\"0.1\" reference=\"ORDER-123\" title=\"Pay with Ezone\" customer_first_name=\"Ali\" customer_last_name=\"Saleh\" customer_phone=\"0910000000\"]\n<\/code><\/pre>\n\nIf the shortcode does not provide customer values, the plugin uses these defaults:<\/p>\n\n
FirstName: WordPress\nLastName: Guest\nPhoneNumber: 0910000000\n<\/code><\/pre>\n\nDevelopers can change the defaults with the ezone_pay_default_customer<\/code> filter:<\/p>\n\nadd_filter('ezone_pay_default_customer', function ($customer) { return ['FirstName' => 'Site', 'LastName' => 'Customer', 'PhoneNumber' => '0910000000']; });\n<\/code><\/pre>\n\nDevelopers can read the stored customer data after payment completion from the ezone_pay_payment_marked_paid<\/code> action:<\/p>\n\nadd_action('ezone_pay_payment_marked_paid', function ($order_reference, $payment) { $first_name = $payment['customer']['FirstName'] ?? ''; $phone = $payment['customer']['PhoneNumber'] ?? ''; }, 10, 2);<h3>Payment confirmation<\/h3>\n<\/code><\/pre>\n\nWhen a customer clicks the shortcode button, the plugin creates a single-use Ezone Pay payment link and stores the local payment session in WordPress.<\/p>\n\n
After Ezone Pay sends the customer back to WordPress, the plugin marks the local session as returned and polls Ezone Pay directly using payment-link details and transactions. The selected API key must have permission to create and view payment links.<\/p>\n\n
The local status endpoint is:<\/p>\n\n
\/wp-json\/ezone-pay\/v1\/status\/{order_reference}?status_token={status_token}\n<\/code><\/pre>\n\nThat endpoint returns the current local payment status, such as pending<\/code>, returned<\/code>, or paid<\/code>. The status token is generated by the plugin and stored with the payment session.<\/p>\n\nAfter payment is completed<\/h3>\n\n
When Ezone Pay confirms the payment, the plugin updates the stored payment status to paid<\/code>, records paid_utc<\/code>, and exposes filters\/actions so the site can decide what to show or do next.<\/p>\n\nDevelopers can customize the payment completed message with the ezone_pay_completed_message<\/code> filter, change the success URL with the ezone_pay_success_url<\/code> filter, and provide site-specific content with the ezone_pay_completed_content<\/code> filter.<\/p>\n\nTo run custom site logic after a payment is marked paid, use the ezone_pay_payment_marked_paid<\/code> action:<\/p>\n\nadd_action('ezone_pay_payment_marked_paid', function ($order_reference, $payment) { \/* Update your order here. *\/ }, 10, 2);<h3>External services<\/h3>\n<\/code><\/pre>\n\nThis plugin connects to the Ezone Pay API to create payment links, display the Ezone Pay checkout page, and confirm whether a payment has been completed. This service is provided by Ezone.<\/p>\n\n
The plugin connects to one of these Ezone Pay API endpoints depending on the selected environment mode:<\/p>\n\n
\n- Development:
https:\/\/test.ezonepay.ly<\/code><\/li>\n- Production:
https:\/\/api.ezonepay.ly<\/code><\/li>\n<\/ul>\n\nWhen a visitor clicks the payment button, the plugin sends the configured Ezone Pay API key, payment amount, payment title, optional note, order reference, internal reference, WordPress return URL, and optional customer first name, last name, and phone number to Ezone Pay. This data is sent so Ezone Pay can create a payment link and return the checkout URL.<\/p>\n\n
After the visitor is redirected back to WordPress, the plugin may send the configured Ezone Pay API key, payment link ID, amount, and order reference to Ezone Pay to check payment-link details and payment-link transactions. This data is sent so WordPress can confirm whether the payment was completed.<\/p>\n\n
The checkout itself is loaded from the payment link returned by Ezone Pay. Any payment details entered by the customer inside the Ezone Pay checkout are submitted directly to Ezone Pay and are not processed by this plugin.<\/p>\n\n
Terms of service: https:\/\/ezonepay.ly\/ar\/terms<\/p>\n\n
Privacy policy: https:\/\/ezonepay.ly\/ar\/privacy<\/p>\n\n
Trademark notice<\/h3>\n\n
This plugin uses the Ezone Pay name to identify the payment service it integrates with. Public distribution should only proceed after you confirm that you have permission from the Ezone Pay trademark owner to use the name, brand, and any related marks.<\/p>\n\n\n
\n- Upload the
ezone-pay<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- Activate Ezone Pay<\/strong> in WordPress.<\/li>\n
- Go to Settings > Ezone Pay<\/strong>.<\/li>\n
- Choose the environment mode.<\/li>\n
- Add the development and\/or production API keys.<\/li>\n
- Make sure each API key has the Create Payment Link<\/strong> and View Payment Links<\/strong> permissions enabled.<\/li>\n
- Add the shortcode to a page.<\/li>\n<\/ol>\n\n\n
\nDoes this plugin process card or wallet credentials?<\/h3><\/dt>\nNo. The plugin creates Ezone Pay payment links and embeds the returned checkout URL.<\/p><\/dd>\n
Why does the payment page stay on \"waiting for confirmation\"?<\/h3><\/dt>\nWordPress has not yet confirmed the payment. Make sure the API key can view payment links and transactions.<\/p><\/dd>\n
Why is the iframe blank or blocked?<\/h3><\/dt>\nThe Ezone Pay checkout page may be using frame-blocking headers. Ezone Pay must allow the merchant domain for iframe checkout.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.1.0<\/h4>\n\n\n- Initial release.<\/li>\n<\/ul>","raw_excerpt":"Create Ezone Pay payment links from WordPress and display checkout in an embedded iframe.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/318526","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=318526"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/ezonepay"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=318526"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=318526"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=318526"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=318526"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=318526"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=318526"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}