FormPays Pro – Payment Form, Contact Form & Custom Form Builder

Changelog

1.2.13

• New: Multiple amount options can list products. Each product has an image, a name, a base price, and a sale price. The visitor chooses one and pays the sale price when it is set, otherwise the base price.
• New: Amount label sets the heading above those products. Leave it empty to use Select amount.
• Improvement: UPI QR Code shows the QR code beside the payment instructions. The UTR field uses the width of that column. On a narrow screen they stack.
• Improvement: When a form has only one payment method, it does not ask the visitor to choose a method.
• Improvement: The transaction screen shows the product the visitor chose. A custom amount is shown with the other answers.
• Bug fix: Activating the plugin creates its database tables on a new site.

1.2.12

• New: The FormPays Pro Form block builds a form in the page editor. Each field is its own block. Saving the page saves a real form, with entries and a shortcode. An existing form can be loaded into the block. New form clears the block and leaves the saved form in place.
• New: Form width can be full width, a centered box, or a fixed width in pixels. Set it in the form editor or in the block.
• New: Form protection can require the visitor to be logged in, or require a password, before the form is shown.
• New: UPI QR Code takes a payment from a UPI ID. The form shows the QR code. The visitor pays and enters the 12-digit UTR. The payment stays on hold until you confirm it. There is no test mode.
• New: Offline Payment takes a bank transfer, wire, NEFT, or RTGS. The form shows the account. The visitor enters the transfer date, the bank reference, and a proof file. The payment stays on hold until you confirm it. There is no test mode.
• Improvement: Offline Payment accepts currencies for major countries, and each one has a currency symbol. The amount on a form uses the currency selected for that form.
• Improvement: IFSC is optional on Offline Payment.
• Improvement: Offline Payment and UPI QR Code use the same Confirmation settings as a form that does not collect a payment. Set the message, where it appears, and whether the form stays on the page, opens a WordPress page, or opens a custom URL.
• Improvement: A form with a list of amounts shows those choices on the form.
• Improvement: The block lists only integrations that are turned on.
• Improvement: Half and third width fields sit side by side in the block editor.
• Improvement: Offline Payment and UPI QR Code have colored icons on the Payment screen.
• Improvement: Accessibility Features and the shortcode sit in two columns on a wide screen and one under the other on a small screen. The shortcode has a copy icon.
• Bug fix: The WordPress admin menu stays in front of the form editor.
• Bug fix: The selected payment check no longer covers Bank transfer or UPI.
• Bug fix: Proceed to Payment starts an Offline Payment or a UPI QR Code payment.
• Bug fix: A password form is no longer submitted as a normal form.

1.2.11

• Bug fix: A Section Divider shows the divider on the form. It no longer shows a text input.
• Bug fix: The public form shows the form name with the description. Shown is the default. Hidden leaves both off the form.
• Bug fix: Payment success, failure, and cancel pages use the active theme’s type and buttons.
• Bug fix: The forms list action icons stay on the same row line as the rest of the form.
• New: Integrations can send a submission to WhatsApp through the WhatsApp Cloud API when a phone number ID and token are saved.
• New: An Empty Spacer field adds a gap between fields. Set the height in pixels. Visitors see only the space. A new spacer is named Empty Space.
• New: Each form has an Appearance section on the Form tab. A CSS class and custom CSS apply to that form only.
• New: An Address field can suggest addresses from Google. Save the API key under Settings → Google → Address autocomplete, then turn on Suggest addresses from Google for that field. Optional country codes limit the suggestions.
• New: Analytics shows a line chart and two donut charts for the dates you choose: submissions over time, complete versus incomplete, and desktop, mobile, and tablet. Each summary card can switch metric and compares with the previous period.
• Improvement: Editing a form shows Back to Forms and Update Form. Start from Scratch and Quick Template stay on a new form.
• Improvement: The forms list shows how many submissions each form has. Edit, Duplicate, Preview, and Delete are icons. The shortcode sits in one box with a copy icon.
• Improvement: The shortcode is [formpays_pro id="123"]. A page that already uses [formpays_pro_payment_form id="123"] still shows the same form.
• Improvement: Coupons & Taxation is a tab under Settings. The old Coupons menu address opens that tab.

1.2.10

• New: Settings → Google Analytics can send form events to the tag already on the site, or load a tag when a Measurement ID is saved. A contact form success is a lead. Starting a payment is begin checkout, and the paid return page is a purchase. Names, email addresses, and field answers are not sent.
• New: Text, email, phone, website, number, message, date, time, coupon, and custom amount fields can show a prefix and a suffix. Each one can be short text or an icon. The field editor shows a sample before you save.
• New: A field label can be Default, Inline, Top, Bottom, Left, Right, or Hide. Hide keeps the label for screen readers and does not show it on the form.
• New: Notification & SMTP can ignore certificate verification. No certificate file is stored.
• New: Settings → Spam protection can use a hidden field, a minimum time before submit, a country allow or deny list, and a keyword list. The spam check can be Cloudflare Turnstile, Google reCAPTCHA, hCaptcha, or Akismet. Each form can keep those plugin settings or replace them under Settings → Protection.
• New: Each form has a Confirmation tab. A form that does not collect a payment can show your message in the form, as a toast, or as an alert, at the top or bottom. It can then stay on the page, open a WordPress page, or open a custom URL.
• New: A payment form can choose its own success page and failure page. After a successful payment, the visitor can download a receipt from the success page.
• Improvement: The selected field shows Move, Up, Down, Edit, Duplicate, and Delete. The first field hides Up. The last field hides Down.
• Improvement: Built-in templates add a prefix or suffix on name, email, phone, invoice number, quantity, date, and coupon fields.
• Improvement: The Add template dialog stays inside the screen. The amount stays hidden until Collect a payment is checked.
• Improvement: The final button label and the clear button stay on the Form tab.
• Improvement: When payment collection is on, Confirmation shows the success page, the failure page, and the receipt. The thank-you message and the final button action stay available when payment is off.

1.2.9

• Bug fix: Saving a form keeps Apple Pay and Google Pay when those methods are checked. Adyen offers the methods selected on the form.
• Bug fix: The first Save Field adds the field once.
• Bug fix: A fixed amount stays the amount set in Form Settings. The payment step no longer shows 0.00.
• Bug fix: The coupon input uses the same style as the other fields, and it appears only when the form includes a Coupon code field.
• New: Tax rules follow the customer’s country and state. Set the country and State of service under Coupons & Taxation. A rule can be removed. Add India GST rules inserts CGST with SGST, and IGST. With no rules, the receipt shows the amount paid and does not add tax.
• New: A Coupon code field checks the code against the form, expiry, usage, and minimum. Apply does not use up the code. Checkout uses it when the payment starts.
• New: Payment is its own menu, after Integrations.
• New: Spam Protection can pause repeated failed payments from the same email or IP. The limit, the time window, and the pause length can be changed. An allowed email or IP can keep paying. A successful payment clears the pause.
• New: Transactions can be filtered by form. All forms is the default, and the export uses the same filter.
• New: Analytics opens on every form. Choose one form to limit the counts, the event list, and the export.
• New: Each form step can name its Next button. A conditional rule can skip a step.
• New: A form can choose which connected integrations run. The integration screen keeps a short delivery log when a send fails.
• New: Global Information can delete this plugin’s data when the plugin is deleted.
• Improvement: Coupons & GST is now Coupons & Taxation. Tax rules are cards, and the second tax name fills the row when the rate is split. The coupon list matches the transactions table.
• Improvement: Built-in templates use form steps and column widths. Payment templates include a coupon field. Templates can be previewed, and you can add, import, and export your own.
• Improvement: Field types are listed in alphabetical order. The form shortcode is shown under Accessibility Features after the form is created.
• Improvement: Analytics summary cards use the same pastel colors as the dashboard.
• Improvement: The SMTP email log uses WordPress pagination, 20 rows at a time. Bulk actions and Clear log are removed from that log.
• Improvement: Payment email settings stay in Notification & SMTP. Spam Protection no longer repeats that email address block.

1.2.8

• The Adyen icon on the gateway settings screen uses Adyen green, so the letter stays visible.
• Form fields can include help text, a website address, and a consent checkbox. Number fields can set a minimum, maximum, and step.
• Dropdown, radio, and checkbox options can use Label|value when the stored answer should differ from the label. Phone numbers may include spaces, dashes, and parentheses.
• Date, file, address, rating, slider, HTML, section, and calculation settings are saved with the field.
• Checkout protection and signed notifications are on the Settings screen. Site key and secret key appear for Turnstile or reCAPTCHA, with a link to the page that issues them. Each gateway links to the page that issues its keys. Server limits are at the bottom of Settings.
• A gateway switch turns green as soon as it is on, and gray as soon as it is off. An enabled gateway shows Production Live or Sandbox Test, and Integration Info says whether live keys or test keys are in use.
• The forms list keeps the counts together, shows each form’s details on one line, and shows Not set when no gateway is chosen.
• Dragging a field stays with the pointer. Editor shortcuts use Option+Shift on Mac and Alt+Shift on Windows: N adds a field, S saves, B toggles bulk select, A selects all fields, and Esc cancels.
• Conditional logic can add a rule group. A rule shows, hides, enables, or disables a field when another field matches, and the public form applies those rules.
• The Start from Scratch and Quick Template icons line up with their labels.
• The same form can be inserted from the FormPays Pro Form block, and from Elementor, Divi, Beaver Builder, WPBakery, and SiteOrigin when that builder is active.
• Integrations is its own menu. A form can send to a webhook, Zapier, Make, Pabbly, n8n, Integrately, IFTTT, Slack, Telegram, Mailchimp, Brevo, MailerLite, ActiveCampaign, FluentCRM, MailPoet, or Google Sheets. Contact form success is included.
• Templates is its own menu. Choose a category, then use the template to create that form and open it in the editor.
• A Form Step field splits a form into steps with Previous, Next, and Submit. The Multi-step template includes those steps.
• Email notifications use the same list and detail layout as Settings.
• An empty form shows Add Field instead of the drag-and-drop notice.

1.2.7

• Adyen payment links for cards, Apple Pay, and Google Pay. The webhook must send AUTHORISATION notifications, signed with the HMAC key.
• The FormPays Pro Form block inserts a form from the editor.

1.2.6

• Stripe Checkout for cards, Apple Pay, and Google Pay. Apple Pay and Google Pay appear when the customer’s device supports them.
• A Stripe subscription bills later periods. Listen for checkout.session.completed and invoice.paid so those payments are recorded.
• Refund a Stripe payment from the transaction screen.

1.2.5

• Invoice numbers: a successful payment receives the next number. Set the prefix under Coupons & GST.
• Pending payments: once an hour, a pending checkout is confirmed with the gateway and marked successful only when the amount and currency match.
• Spam protection: checkout includes a hidden field. Turnstile or reCAPTCHA can be required from Coupons & GST.
• Notifications: a success, failure, or refund can send a signed JSON body to a URL you choose.
• Renewals: a Razorpay or PayPal subscription bills later periods automatically. If that cannot be started, the customer still receives a payment link.

1.2.4

• The CSV export is built in memory. Plugin Check no longer reports a filesystem error for closing that stream.

1.2.3

• Export formats selected on a form can be downloaded from that form. Auto export emails those files on the daily, weekly, or monthly schedule.

1.2.2

• Single payment charges the full amount. Installments charge the first share now and collect the rest from a signed link. Subscriptions charge one period now and email a link for the next period.
• Partial payments let the customer save the form and pay later from an emailed link.
• Currency conversion shows approximate amounts in the gateway’s other currencies. The charge stays in the form currency.
• Payment scheduling lets the customer pick a date and time slot. The payment link is emailed when that time arrives.

1.2.1

• Coupons & GST opens its admin screen instead of the site home page.
• Plugin Check compatibility for a WordPress 6.1-only cache call, the Razorpay retry script, translator comments, and an invalid-link message.

1.2.0

• Refund a successful payment, in full or in part, from the transaction screen.
• Download a PDF receipt. GST can show taxable value and CGST/SGST or IGST. The amount collected is treated as tax-inclusive.
• Add coupon codes with an optional form, minimum amount, expiry, and usage limit.
• Email a customer who leaves checkout pending, with a link to continue.
• Retry a failed or pending payment from the result page or the email without creating a second transaction.

1.1.4

• Payment amounts are calculated on the server. A submitted total cannot lower the charge.
• Return URLs and webhooks confirm the paid amount and currency before a transaction is marked successful.
• Razorpay webhooks require a valid signature. PhonePe, PayPal, Instamojo, and PayU callbacks are confirmed with the gateway before success is recorded.
• The test gateway accepts a payment only while test mode is on.
• Gateway secrets are encrypted and are not stored in plain text when encryption fails.
• Form submissions are sanitized and rate limited, and payment redirects are limited to this site or the payment gateway.
• Customer details are escaped on payment result pages and in notification emails.
• Tested with WordPress 7.1.

1.1.3

• Added email notifications for payment success and failure, with editable templates and a test email.
• Razorpay checkout receives the selected payment method and a formatted phone number.
• Fixed the transaction time on the success page and a deprecated dynamic property warning.

1.1.2

• Admin redirects use wp_safe_redirect().
• Admin screens no longer overwrite the WordPress page, status, or per_page globals.
• Nonce checks cover the admin actions.

1.1.1

• Moved inline admin scripts into files.
• Formatting and documentation updates for the WordPress coding standards.

1.1.0

• Added the PhonePe gateway.
• Stronger webhook and nonce checks.
• Admin and form builder updates.

1.0.0

• Initial release with Razorpay, PayU, the form builder, transactions, email notices, and webhooks.