Title: Simple Payment Author: Ido Kobelkowsky Published: 2019-10-10 Last modified: 2026-10-10 --- Szukaj wtyczek ![](https://ps.w.org/simple-payment/assets/banner-772x250.png?rev=3318371) ![](https://ps.w.org/simple-payment/assets/icon-256x256.png?rev=3318371) # Simple Payment Autor: [Ido Kobelkowsky](https://profiles.wordpress.org/idokd/) [Pobierz](https://downloads.wordpress.org/plugin/simple-payment.2.5.21.zip) * [Szczegóły](https://pl.wordpress.org/plugins/simple-payment/#description) * [Recenzje](https://pl.wordpress.org/plugins/simple-payment/#reviews) * [Instalacja](https://pl.wordpress.org/plugins/simple-payment/#installation) * [Rozwój](https://pl.wordpress.org/plugins/simple-payment/#developers) [Wsparcie](https://wordpress.org/support/plugin/simple-payment/) ## Opis **Selling something shouldn’t require a full shopping cart.** Simple Payment turns any WordPress post, page, block, form or button into a ready-to-pay product or service in minutes — and routes the money through the payment gateway you already trust. No bloated store to configure, no checkout to rebuild: just a shortcode (or a block, or an Elementor widget) and you are taking payments. From a single „Donate” button to installment plans, saved cards, subscriptions and multi-gateway checkouts, Simple Payment scales from a personal blog to a commercial site — while keeping sensitive card data out of your database. #### Why you’ll love it * **Sell in minutes, not days.** Drop one shortcode on any page and you have a working, styled payment form. Post/page titles become the product name and a custom field becomes the price — automatically. * **Use the gateway you already have.** One consistent form and workflow in front of many gateways — switch providers without rebuilding your pages. * **Built for real money flows.** Installments, monthly subscriptions / recurring, saved-card tokenization, refunds, invoices/receipts, and automatic transaction verification. * **Beautiful, flexible forms.** Multiple templates (Bootstrap, Legacy, Donation, free-amount), inline, IFRAME or modal display, and full support for your own theme templates. * **Privacy first.** PCI-DSS friendly: card data is masked/redacted before anything touches the database, and old records can be auto-archived and purged. * **Developer friendly.** A rich set of actions and filters, a documented Engine API to extend any gateway or build your own, plus a full transactions log with filtering and CSV export. #### Supported payment gateways (Engines) PayPal, Cardcom, iCount, PayMe, iCredit, CreditGuard, Meshulam, YaadPay, Credit2000, WooCommerce (third-party site), plus a Custom engine for anything else and a Test engine for development. #### NEW: Sell on one site, charge on another (WooCommerce engine) The **WooCommerce engine** lets your site take a purchase and hand the actual payment off to a **separate, third-party WooCommerce store** over its REST API — perfect for agencies, marketplaces, franchises and multi-brand operators who want a central„ storefront” and one billing store that owns the gateways, invoices and bookkeeping. * The customer clicks Buy on your site; Simple Payment creates the order on the remote WooCommerce store with the correct total and customer details. * The shopper pays on the remote store (in a redirect, popup or modal) using whatever gateways that store has enabled. * A bundled **Companion mode** on the receiving store validates and keeps the originating parameters, can auto-complete paid orders, silences the remote store’s duplicate customer/admin emails for outsourced requests, and sends the customer straight back to your site when payment succeeds. * You keep a full record of every transaction on the originating site, with automatic status verification. #### Works with your favorite tools Gutenberg block editor, Elementor, WooCommerce, WPJobBoard, GravityForms and Form Maker — plus **Zapier** to trigger workflows (CRM, email, spreadsheets, fulfilment) on every payment. #### What you can build * One-click „Buy” / „Donate” buttons anywhere on your site * Pay-what-you-want donation forms with a free-entry amount * Membership, course or service checkouts on a single landing page * Installment plans and monthly subscriptions * Central storefront that bills through a separate WooCommerce store Currently on Beta: PayMe – please contact if you require assistance. Soon to be released: Pelecard, Tranzila. PS: You’ll need a [Simple Payment API key for advanced gateways](https://simple-payment.yalla-ya.com/get/) to use it. Keys are available for personal blogs; single domain, multiple domains, businesses and commercial sites. ### Feedback and Support I would be happy to receive your feedback to improve this plugin. Please let me know through [support forums](https://wordpress.org/support/plugin/simple-payment/) if you like it and please be sure to leave a review.. Also you can contact me on my personal page [Ido Kobelkowsky](https://wordpress.org/support/users/idokd/) or even visit [Github](https://github.com/idokd/wp-simple-payment) of Simple Payment where you can find all the development code of this plugin. I hope it is useful for you and look forward to reading your reviews! 😉 Thanks! ### Advanced Configuration: Theme Custom Payment Processing To write your own payment processing integration, to be plugin, read the information at this link: [https://simple-payment.yalla-ya.com/](https://simple-payment.yalla-ya.com/) you will require to write a simple php class that Pre Process, Process and Post Process the transaction with your your payment gateway. ## Zrzuty ekranu [⌊Create Payment Page; use Admin -> Settings -> Reading to define which is your Payment Page.⌉⌊Create Payment Page; use Admin -> Settings -> Reading to define which is your Payment Page.⌉[ Create Payment Page; use Admin -> Settings -> Reading to define which is your Payment Page. [⌊Configure the gateway parameters, you may use one of our many preinstalled gateways.⌉⌊ Configure the gateway parameters, you may use one of our many preinstalled gateways .⌉[ Configure the gateway parameters, you may use one of our many preinstalled gateways. [⌊Integrate our [simple_payment] shortcode on that page, to show one of our wonderful forms⌉⌊Integrate our [simple_payment] shortcode on that page, to show one of our wonderful forms⌉[ Integrate our [simple_payment] shortcode on that page, to show one of our wonderful forms [⌊Track each transaction, keep record of parameters sent and responds.⌉⌊Track each transaction, keep record of parameters sent and responds.⌉[ Track each transaction, keep record of parameters sent and responds. [⌊Payment Form example (our Legacy form) - we have bootstrap ready, donation etc.⌉⌊ Payment Form example (our Legacy form) - we have bootstrap ready, donation etc.⌉[ Payment Form example (our Legacy form) – we have bootstrap ready, donation etc. [⌊REMEMBER! Set the Payment Page so you can enjoy the plugin.⌉⌊REMEMBER! Set the Payment Page so you can enjoy the plugin.⌉[ REMEMBER! Set the Payment Page so you can enjoy the plugin. [⌊Gutenberg Editor support - easy configuration for your multiple payment forms.⌉⌊ Gutenberg Editor support - easy configuration for your multiple payment forms.⌉[ Gutenberg Editor support – easy configuration for your multiple payment forms. [⌊Tranaction Log⌉⌊Tranaction Log⌉[ Tranaction Log [⌊Extended configuration⌉⌊Extended configuration⌉[ Extended configuration [⌊PCI-DSS ready, masking data directly in database⌉⌊PCI-DSS ready, masking data directly in database⌉[ PCI-DSS ready, masking data directly in database ## Bloki Wtyczka dodaje 1 blok. * Simple Payment ## Instalacja 1. Upload the Simple Payment plugin to your site, Activate it, then enter your [Simple Payment API key](https://simple-payment.yalla-ya.com/get/). 2. Select Payment Page where you will have the Payment Form integrated 3. add shortcode on the Payment Page 4. Activate your Payment Processing on the Admin Menu: Settings -> Simple Payment 5. That’s it, track your payments on the Payments Admin Menu log. ## Najczęściej zadawane pytania ### Which Payment Gateway this plugin support? Out of the box it supports PayPal, Cardcom, iCount, PayMe, iCredit, CreditGuard, Meshulam, YaadPay, Credit2000 and a third-party WooCommerce store, plus a Custom engine so you can add your own — with new gateways added regularly. ### Do I need WooCommerce or a shopping cart? No. Simple Payment works on its own — a shortcode, block, Elementor widget or button on any page is enough. It also integrates with WooCommerce (both as a WooCommerce gateway and by sending purchases to a separate WooCommerce store) if you want it. ### Can I take the payment on a different WooCommerce website? Yes. Choose the WooCommerce engine and point it at a third-party WooCommerce store’s REST API (consumer key/secret). Simple Payment creates the order there with the correct total, the shopper pays on that store, and they are returned to your site automatically. Install Simple Payment on the receiving store too and enable Companion mode so it recognises the incoming orders, picks the gateway, optionally auto-completes them, mutes duplicate emails and redirects the buyer back. Ideal for agencies, marketplaces, franchises and central-billing setups. ### Does it support installments, subscriptions and saved cards? Yes, where the selected gateway supports them: installment plans, monthly/recurring subscriptions, saved-card tokenization and refunds are all available. ### Can I display the payment in a popup or IFRAME? Yes. Forms can be shown inline, in a modal, or in an IFRAME. (When paying through a third-party WooCommerce store, a redirect or popup is recommended, since external gateways such as Stripe cannot complete card authentication inside a cross-domain IFRAME.) ### How does Simple Payment complies with PCI-DSS When a payment is passed through the plugin, it restricts the use of sensible data to the minimum possible, avoids any replication of variables and data, and upon saving on the database is masks and hides the data so no sensible data is saved in the database. Additional it allows you to automaticaly purge any records older the X days. ### Can I work with Simple Payments and other plugins Simple Payment is ready to be extended, it exposes actions and filters (add_action& add_filters), to hook in differnet parts of the payment process. You can also extend any of the existing Payment Gateways (Engines) or write your own Custom Engine, and finally you can integrate Simple Payment with [Zapier](https://zapier.com/developer/public-invite/66167/f63e9e617b9e5e534c26c308f15087ee/) ### How can I report security bugs? You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team helps validate, triage and handle any security vulnerabilities. [Report a security vulnerability.](https://patchstack.com/database/vdp/21aaae52-b279-4f4e-bd4a-94c3c88c3188) ## Recenzje ![](https://secure.gravatar.com/avatar/721e8ac1a9c9d840db660a0ccec807b7501340bd17309e785120e71b9788a9dc? s=60&d=retro&r=g) ### 󠀁[Great plugin and incredible support!](https://wordpress.org/support/topic/great-plugin-and-incredible-support-11/)󠁿 [Stratus](https://profiles.wordpress.org/airbenderlab/) 2022-05-03 I've been using this one for a while now, and it works like a charm. When it dosen't and I need support I know it's just one email away from me and the creator of the plugin will try his best to help and solve it. Never seen anything like it! ![](https://secure.gravatar.com/avatar/302ac78029ace556d6559affe61d63d76a4ac18d748fea1a4915ec737ce120cf? s=60&d=retro&r=g) ### 󠀁[great plugin and best developer services ever](https://wordpress.org/support/topic/great-plugin-and-best-developer-services-ever/)󠁿 [hmeonot](https://profiles.wordpress.org/hmeonot/) 2019-12-07 i just couldn't wait to tell about this great tool called "simple payment" i was lost until i found this talented developer he just can take every page and every plugin and turn it into a payment page that is just amazing it was a delight to work with you Ido Kobelkowsky we will defiantly continue to work together in the future so if you need payment on your wordpress plugins woocommers form maker wp job board and many more as long as you can think of and you name it and ido will make it work for you ![](https://secure.gravatar.com/avatar/c9656a87006a9607f1a36953630c13e66396530b93493af211051fd2e94e5e21? s=60&d=retro&r=g) ### 󠀁[I am just loving it, every moment of it](https://wordpress.org/support/topic/i-am-just-loving-it-every-moment-of-it/)󠁿 [Ido Kobelkowsky](https://profiles.wordpress.org/idokd/) 2019-10-23 I know I am very subjective in my opinion, I am the developer of the plugin – but I still think I get to put a review of it; SO! I love working on this plugin, it is challenging, fun and truly simplifies my life while working on client's sites and other projects, I have learned a lot of how to optimize the the plugin to work as much as possible with the Wordpress platform and still obtain the exact results I wanted on the features. [ Przeczytaj 3 recenzje ](https://wordpress.org/support/plugin/simple-payment/reviews/) ## Kontrybutorzy i deweloperzy „Simple Payment” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki. Zaangażowani * [ Ido Kobelkowsky ](https://profiles.wordpress.org/idokd/) Wtyczka „Simple Payment” została przetłumaczona na 1 język. Podziękuj [tłumaczom](https://translate.wordpress.org/projects/wp-plugins/simple-payment/contributors) za ich wkład. [Przetłumacz wtyczkę “Simple Payment” na swój język.](https://translate.wordpress.org/projects/wp-plugins/simple-payment) ### Interesuje cię rozwój wtyczki? [Przeglądaj kod](https://plugins.trac.wordpress.org/browser/simple-payment/), sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/simple-payment/) lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/simple-payment/) przez [RSS](https://plugins.trac.wordpress.org/log/simple-payment/?limit=100&mode=stop_on_copy&format=rss). ## Rejestr zmian #### 2.5.21 * Security (YaadPay): the payment callback is now always confirmed with YaadPay server-side (APISign / VERIFY) before a transaction is completed; the request approval code (ACode) is never accepted as proof of payment. Verification uses the dedicated APISign Verification Key when set, otherwise the API Key that the hosted-page flow already requires, so no new configuration is needed on existing terminals. This removes the previous opt-in behaviour where the callback was trusted when no verification key was set. **Test a real YaadPay payment before releasing: if VERIFY cannot confirm the transaction, the payment will not complete.** #### 2.5.20 * Security (iCount): the payment callback now fails closed. iCount is a direct engine that charges during the request and never completes through the public op=ok callback, but that callback could still reach post_process() for a pending transaction; the recurring/provider branch and the invoice-document branch returned success without any server-side check, taking the subscription flag from the request. post_process() now completes only when this request actually charged the card (process() confirmed it) or iCount verifies the transaction server-side.** Test a real iCount payment – one-time, and recurring/provider if used – before releasing.** #### 2.5.19 * Security (YaadPay): added an optional „APISign Verification Key” setting. When it is set, the payment callback is confirmed with YaadPay server-side (APISign/ VERIFY) by re-posting the signed transaction fields, and the payment completes only if the signature validates – closing a path where a crafted callback with an approval code could mark a pending transaction paid. When the field is left empty the gateway response is trusted as before (existing behaviour), so current installs are unaffected until they opt in. **Test a real YaadPay payment with the APISign key set before relying on verification.** #### 2.5.18 * Security (CreditGuard): in direct (non-redirect) mode the payment callback now confirms the transaction with CreditGuard server-side (inquireTransactions, by tranId) before completing, instead of trusting the status and authNumber sent in the request. The confirmation code is taken from the gateway’s response; a transaction CreditGuard does not report as approved now raises instead of completing. Redirect mode already validated the response MAC and confirmed server-side. ** Test a real CreditGuard direct-mode payment before releasing.** #### 2.5.17 * Security (Meshulam): the payment status/IPN callback now confirms the transaction with Meshulam server-side (getPaymentProcessInfo) and takes the confirmation code (asmachta) from that response, instead of trusting the status and asmachta sent in the request. An unauthenticated callback can no longer mark a pending transaction paid. **Test a real Meshulam payment (including Bit and subscriptions) before releasing.** #### 2.5.16 * Security (PayMe): the payment callback now confirms the sale with PayMe server- side (get-transactions API, requiring transaction_error_code 20000) using the sale id stored for the transaction, instead of trusting the status / auth number sent in the request. **Test a real PayMe payment before releasing.** #### 2.5.15 * Security (Cardcom): the payment callback now confirms the deal with Cardcom server- side (indicator API, by lowprofilecode) before completing, instead of trusting a response code from the request. The previous check read a misspelled request key, so an unset value passed and an unauthenticated callback could mark a pending transaction paid. **Test a real Cardcom payment before releasing.** #### 2.5.14 * Security: the Gravity Forms IPN endpoint (page=gf_simplepayment_ipn) no longer completes a payment just because the entry has an active feed – it now requires a matching Simple Payment transaction that is recorded as successful for that entry and amount, so the public endpoint cannot mark an unpaid entry paid * Cardcom: fixed an undefined variable in verify() that broke server-side transaction verification in live mode (it referenced the wrong variable for the terminal/ username), so pending Cardcom transactions can be verified again #### 2.5.13 * Security: fixed a stored XSS on the Payments admin screen – transaction fields shown in the list (e.g. user agent) were rendered unescaped when 40 characters or shorter, so an attacker-supplied value could run script in an administrator’s browser. All values are now escaped * Security: the payment success action is now fired only when the payment is actually verified/completed (post_process returns true), and the transaction’s source / source_id / engine / amount are taken from the stored record rather than the request – preventing a request from completing or retargeting an unpaid payment( e.g. a Gravity Forms entry) #### 2.5.12 * WooCommerce companion: email suppression for incoming orders is now prefix-based– the enabled filter is registered for every WooCommerce email once the mailer loads (customer_* treated as customer, everything else as admin/store), so email types added in future WooCommerce versions are covered automatically without maintaining an explicit list. Only emails that carry an incoming order are suppressed; unrelated emails (password resets, stock alerts) are untouched #### 2.5.11 * WooCommerce companion: also suppress the customer-facing failed / cancelled order emails (customer_failed_order, customer_cancelled_order) and the Point of Sale customer emails (customer_pos_completed_order, customer_pos_refunded_order) for incoming orders when „Disable Customer Emails” is on. WooCommerce added the customer failed-order email in a recent version, so it was still sent even though the admin failed-order email was already blocked #### 2.5.10 * WooCommerce companion: incoming orders are now recorded in the currency they were placed in on the source site (from the sp_source_currency meta), instead of this store’s currency – so a 500 MXN order no longer reads / is paid as 500 USD. Filterable via sp_wc_incoming_set_currency; only applied when the code is a valid WooCommerce currency #### 2.5.9 * WooCommerce gateway: pass the order’s currency along with its total. It was never mapped, so payments fell back to the global Simple Payment currency setting – e.g. a 500 MXN order was created / charged as 500 USD on a remote WooCommerce store * WooCommerce engine / companion: the purchase’s original amount and currency ( as placed on the source site, before any conversion filter) are sent as sp_source_currency/ sp_source_amount meta on the remote order and kept by the companion * WooCommerce companion: skip WooCommerce’s guest email verification on the pay for order / order received pages for incoming orders opened with their order key (new „Skip Email Verification” setting, enabled by default). WooCommerce only waives that check for 10 minutes after the order is created, so a re-opened payment link (or a return after a failed attempt) asked the customer to type the billing email the source site sent before showing any gateway #### 2.5.8 * Fraud Detection: the WooCommerce checkout guards are now registered on plugins_loaded, so temporary and permanent blocks are actually applied – the feature file loads before WooCommerce, so the previous load-time function_exists( 'WC’ ) check was always false and no block was ever enforced at checkout * Fraud Detection: new Simple Payment adapter („Enable Simple Payment Fraud Detection”, on by default) – every payment processed by the plugin itself (payment form / popup, WooCommerce gateway including pay-for-order links, GravityForms…) is refused at pre-process when the payer’s email / phone / IP is blocked; failed payments count towards a block and a genuinely successful one clears it. Until now only the WooCommerce checkout form was checked, so a blocked email could still pay an existing order through its payment link * Fraud Detection: added an „Open blocked / pending list” debug view – shows active/ permanent blocks together with identities still accumulating towards a block, to trace and debug detection #### 2.5.7 * Security: hardened the payment-completion callbacks against a payment bypass – the callback now binds each transaction to the engine that created it (read from the stored record, not the request) and only completes a still-pending transaction, and the payment engines verify server-side and fail closed (PayPal confirms the payment is approved with a matching amount/currency; Credit2000 and iCount verify server-side; the mock Test engine can no longer be selected from a request on a live site; engine names are validated against the supported list) * Security: fixed reflected XSS on the Payments admin screen (date-range filter values escaped and validated, sorting restricted to known columns) and stored XSS via the [simple_payment] shortcode / form „target” attribute * WooCommerce: declared compatibility with High-Performance Order Storage (HPOS/ custom order tables) and the Cart & Checkout Blocks, and access order data through the order object (CRUD) #### 2.5.5 * Security: the payment callback now binds each transaction to the engine that created it (read from the stored record, not the request) and only completes a transaction that is still pending, blocking attempts to force a weaker gateway’s verification (e.g. engine=PayPal) or to complete/replay another transaction * Security: payment engines now fail closed – PayPal confirms the payment is approved( and the amount/currency match) with PayPal before completing, Credit2000 and iCount verify server-side instead of trusting the callback, the mock Test engine can no longer be selected from a request on a live site, engine names are validated against the supported list, and the base engine no longer reports success by default * Security: fixed reflected XSS on the Payments admin screen (the date-range filter values are now escaped and validated, and sorting is restricted to known columns) * Security: fixed stored XSS via the [simple_payment] shortcode / form „target” attribute (now escaped on output) * WooCommerce: declared compatibility with High-Performance Order Storage (HPOS/ custom order tables) and the Cart & Checkout Blocks, so the plugin is no longer listed as incompatible with current WooCommerce features. Order data (provider url, transaction id, refund concept) is now read and written through the order object (CRUD), keeping WooCommerce and WooCommerce Subscriptions working on the latest versions with HPOS enabled #### 2.5.1 * Added WooCommerce payment engine: create the purchase as an order on a third party WooCommerce website via its REST API, and open the returned redirect url in an iframe / popup for payment * Added WooCommerce companion handling for the receiving store: exposes / validates/ keeps the sp_* order parameters on the REST API, can auto complete paid orders( skipping processing), and redirects the customer back to the originating site once the order is paid * WooCommerce companion: the receiving store selects the gateway for incoming orders( the source site does not need to know the remote gateways, and its own Simple Payment gateway may be used); unknown incoming payment methods are cleared so the customer can choose on the payment page * WooCommerce companion: flags to disable WooCommerce customer and/or admin emails for orders received from the source site (outsourced payment requests) * Added an Experimental Features framework (Settings > Experimental): toggle features on/off, each loads on plugin start with its own settings * Moved the Zapier integration into an experimental feature with an Enable toggle, and it now shows the ready-to-use Zapier endpoint URL (including the API key) in the settings * New experimental feature „Fraud Detection”: blocks further payment attempts ( hides payment methods and shows a custom message) after repeated failed payments that share the same identity within a timeframe, with a cooldown, role whitelist and an option to exempt registered users. Each identity field (email, billing phone, IP address, user agent) has a matching mode – Default, Cluster (linked with other clustered fields) or Primary (counted on its own) – so failed attempts that share any clustered value are counted as one cluster (e.g. X/Y, then X/Z, then B/Y count as 3). Defaults to Email + Phone + IP clustered over a 24 hour window. The engine is integration-agnostic (a WooCommerce adapter is included and toggled by „Enable WooCommerce Fraud Detection”, so the same rules can drive other integrations). Repeat offenders can be escalated to a permanent block after N temporary blocks – stored in the sp_fraud_blocked option as comma-separated clustered keys and manageable from a settings field. Permanent blocks and a key- based whitelist (both field:value lists, e.g. role:subscriber, email:ido@example. com) let you block or always-allow by email, phone, IP or role. A „Detected Blocks” table in the settings lists the auto-created blocks with their count, last time and status (active / expired / permanent) #### 2.5.0 _Release Data – 14 Jul 2026_ * Fixes on gravityforms integration * Improvements on woocommerce integration * Logo support for CreditGuard integration * Tested to latest WP version * Security fixes #### 2.4.6 _Release Date – 29 Jun 2025_ * Added Test Engine for testing/dev purposes * Fixed issue with composer and class not found * Tested to latest WP version * Security fixes #### 2.4.2 _Release Date – 29 Jun 2025_ * Better support for Cardcom & GravityForms * Security fixes #### 2.4.1 _Release Date – 26 Jun 2025_ * Security fix, XSS on admin. * Security and bug fixes* Performance Improvment – Seperation of Front-end / Backend code * Fixing issue with Woocommerce Subscriptions forcing tokens on Woocommerce Checkout * Feature: shorten urls when Payment Gateway cannot handle standard url lengths * Tested under PHP 8.4 #### 2.2.2 _Release Date – 9 May 2022_ * CreditGuard Support * Minor bug fixes and improvements #### 2.2.1 _Release Date – 9 May 2022_ * Addition of Multi products flag on GF Feed * Fixed issues with GF multiple products on invoice iCount * Fixed issues with CC Storage iCount ( must have Client Name to enable, or pre-existing client ) #### 2.1.5 _Release Date – 9 Mar 2022_ * Ready for WP 5.9.1 * Support for GF & Multiple Products in invoice Cardcom #### 2.1.0 _Release Date – 6 Mar 2021_ * Fix limit 30 chars for iCount sanity_string #### 2.0.9 _Release Date – 15 Feb 2021_ * Disable composer platform-check #### 2.0.8 _Release Date – 15 Feb 2021_ * Added filter: sp_list_table_columns * Added filter: sp_list_table_column_value * Added filter: sp_admin_sections * Added filter: sp_admin_settings* Added filter: sp_admin_tabs * Added support for columns with jsonq in payments list #### 2.0.7 _Release Date – 30 Dec 2020_ * Support & Tested up to WordPress 5.6 * Support & Tested on PHP 7.4 * Fixed issue with not saving per page on admin transaction list* Enabled filter by date range on admin transaction list * Added created on filters on admin transaction list * Improved and fixed issues with Cardcom payment gateway* Added support to WC Subscription * Beta version with Cardcom & WC Subscription * Added refund function * Added support of old mysql server for TIMESTAMP for modified and created on db tables #### 2.0.0 _Release Date – 5 May 2020_ * Provide Documentation and additional links #### 1.9.7 _Release Date – 5 May 2020_ * Support for WordPress 5.4.1 * Support for WooCommerce 4.1 * General bug fixes and improvements #### 1.9.6 _Release Date – 10 April 2020_ * WooCommerce improvements * settings: „woocommerce_show_checkout”: true – for iframe/modal inside checkout page * settings: „modal_disable_close”: true – for non-closing modal * General bug fixes and improvements #### 1.9.5 _Release Date – 6 April 2020_ * CVV type engines bug on GravityForms * Tests for WordPress 5.4 * * General bug fixes and improvements #### 1.8.2 _Release Date – 10 February 2020_ * Hebrew translation * General bug fixes and improvements #### 1.8.2 _Release Date – 7 February 2020_ * Support for Credit2000 Payment Gateway * Improved error handling * General bug fixes and improvements #### 1.7.9 _Release Date – 23 January 2020_ * Support for GravityForms * General bug fixes and improvements #### 1.7.6 _Release Date – 11 December 2019_ * Adding support to iCredit & PayMe * Support for Elementor Page Builder * Internet Explorer bug fix * Improvement of Gutenberg Editor block type * General bug fixes and improvements #### 1.7.4 _Release Date – 4 December 2019_ * Adding Company field for Cardcom & general usage* Improvement of Gutenberg Editor block type * Bug fix of SQL error after archive/ unarchive on transaction list * General bug fixes and improvements #### 1.7.1 _Release Date – 24 November 2019_ * Bugfix on Cardcom special cases. #### 1.7.0 _Release Date – 24 November 2019_ * Better support for [WPJobBoard](https://wpjobboard.net/)]& WooCommerce * Enable single item receipt in WooCommerce & WPJobBoard * Enable customize product name in WooCommerce & WPJobBoard * Enable iframe, modal & redirect mode in WooCommerce & WPJobBoard * Cardcom flag to minimize information on receipt – will show only minimum necessary information * Enables supports() to Engines * Bugfix on verification process. #### 1.6.8 _Release Date – 12 November 2019_ * Beta support to [WPJobBoard](https://wpjobboard.net/) plugin #### 1.6.7 _Release Date – 12 November 2019_ * Introducing visible and resetable API_KEY * Cron Schedule for Simple Payment maintenance * Auto validate open transactions * Auto fail open transactions after a certain period #### 1.6.5 _Release Date – 11 November 2019_ * Unarchive feature * General improvements and addons code structure #### 1.4.5 _Release Date – 5 November 2019_ Great news! we now support Zapier & WooCommerce, so all Payment Gateways (Engines) can now work transparently in WooCommerce. * Zapier integration; use this link to connect and configure: [Zapier](https://zapier.com/developer/public-invite/66167/f63e9e617b9e5e534c26c308f15087ee/) * WooCommerce enable Simple Payment on your WooCommerce and enjoy the same control of Simple Payment * Shortcode now accept: currency & installments * Stability improvements * General Bug fixes #### 1.4.0 _Release Date – 4 November 2019_ * Introduction of Archive & Purge transaction * Introduction of Beta Zapier integration * Create WordPress User (Secret or Via Register) on payment (pre or post payment) * General Bug fixes #### 1.0.0 _Release Date – 1 October 2019_ * First release ## Meta * Wersja **2.5.21** * Ostatnia aktualizacja **4 dni temu** * Włączone instalacje **40+** * Wersja WordPressa ** 4.6 lub nowszej ** * Testowano do **7.0.7** * Wersja PHP ** 7.4 lub nowszej ** * Języki * [English (US)](https://wordpress.org/plugins/simple-payment/) i [Persian](https://fa.wordpress.org/plugins/simple-payment/). * [Przetłumacz na swój język](https://translate.wordpress.org/projects/wp-plugins/simple-payment) * Tagi * [checkout](https://pl.wordpress.org/plugins/tags/checkout/)[credit card](https://pl.wordpress.org/plugins/tags/credit-card/) [donation](https://pl.wordpress.org/plugins/tags/donation/)[membership](https://pl.wordpress.org/plugins/tags/membership/) [simple payment](https://pl.wordpress.org/plugins/tags/simple-payment/) * [Widok zaawansowany](https://pl.wordpress.org/plugins/simple-payment/advanced/) ## Oceny 5 na 5 gwiazdek. * [ 3 recenzje 5-gwiazdkowe ](https://wordpress.org/support/plugin/simple-payment/reviews/?filter=5) * [ 0 recenzji 4-gwiazdkowych ](https://wordpress.org/support/plugin/simple-payment/reviews/?filter=4) * [ 0 recenzji 3-gwiazdkowych ](https://wordpress.org/support/plugin/simple-payment/reviews/?filter=3) * [ 0 recenzji 2-gwiazdkowych ](https://wordpress.org/support/plugin/simple-payment/reviews/?filter=2) * [ 0 recenzji 1-gwiazdkowych ](https://wordpress.org/support/plugin/simple-payment/reviews/?filter=1) [Twoja opinia](https://wordpress.org/support/plugin/simple-payment/reviews/#new-post) [Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/simple-payment/reviews/) ## Zaangażowani * [ Ido Kobelkowsky ](https://profiles.wordpress.org/idokd/) ## Wsparcie Masz coś do dodania? Potrzebujesz pomocy? [Zobacz forum wsparcia](https://wordpress.org/support/plugin/simple-payment/) ## Złóż datek Czy chcesz wesprzeć rozwój wtyczki? [ Wspomóż wtyczkę ](https://simple-payment.yalla-ya.com/get)