Jotform payment connected but payment or submission not received
An end-to-end Jotform payment checklist for Stripe, Mollie, Square, and similar integrations when the form submits without payment, shows a zero total, runs in test mode, loses the submission, or sends the wrong confirmation.
Do not want to work through every Jotform check yourself? Send the current URL, screenshots, and timeline. We can run the buyer-controlled diagnosis and return a fixed-scope payment-flow test and reconciliation pack.
Payment forms mix calculation, conditional logic, product fields, integration mode, submission state, and gateway state. Use a safe clone or test environment and never paste real card data into screenshots or support notes.
Preserve the live form and integration settings.
Use provider-supported test cards or sandbox mode.
Define one exact expected amount and path.
Follow one submission through every system
A successful form submission is not the same as a successful payment. Track the form submission ID, payment field values, gateway event, transaction ID, final status, and confirmation email as separate checkpoints.
Map product/calculation output into the payment amount.
Check live versus test account connection.
Reconcile Jotform and gateway status by timestamp and ID.
Verify failure and recovery behavior
The form must handle decline, cancellation, retry, duplicate click, and confirmation without recording a paid booking when money was not captured or losing a valid payment.
Test success and failure paths.
Check conditional emails and redirect behavior.
Keep a transaction exception log for unmatched cases.
Technical troubleshooting checklist
Work through the evidence in a controlled order.
Each check defines what a healthy result looks like, what to do when it fails, and what evidence to preserve before the next change.
01
Form and amount checks
Make the expected amount deterministic before testing the gateway.
Document the product, quantity, calculation, coupon, tax/fee, and final payment amount fields.
Healthy result
One selected test path produces the expected nonzero amount before payment.
If it fails
Fix field values, calculation order, or conditions that leave the payment amount blank or zero.
Save as evidence
Redacted field map and expected amount calculation.
Check required conditions and page/card navigation around the payment field.
Healthy result
The payment field is visible and required for every path that promises a paid booking or order.
If it fails
Correct conditions that hide, skip, or bypass payment on a valid order path.
Save as evidence
Condition export/screenshots and path-by-path visibility table.
Verify the integration is connected to the intended provider account, mode, currency, and payment method.
Healthy result
Test uses sandbox/test and production uses the approved live account with compatible currency/methods.
If it fails
Reconnect the correct account or align mode, currency, and method support.
Save as evidence
Connection status and mode with account identifiers redacted.
Clone or version the form before changes and define a rollback point.
Healthy result
The live form remains recoverable and the test form has a clear owner and date.
If it fails
Create a safe copy before editing calculations or integrations.
Save as evidence
Form IDs, version names, change owner, and rollback reference.
02
Transaction and confirmation checks
Trace one success and one controlled failure across Jotform and the payment provider.
Run a provider-supported test payment and record submission ID, amount, currency, and gateway result.
Healthy result
Jotform and the gateway agree on amount, mode, transaction, and success state.
If it fails
Locate the first missing or mismatched ID between form submission and gateway event.
Save as evidence
Test script row, submission ID, gateway event ID, and timestamps.
Test decline/cancel behavior and browser return path.
Healthy result
The user receives a clear failure state and no paid confirmation or fulfilled booking is created.
If it fails
Correct status conditions, redirect, and confirmation logic.
Save as evidence
Failure-path screenshot, submission state, and gateway result.
Verify owner, customer, and supplier notifications use the correct trigger and permitted fields.
Healthy result
Each recipient receives the intended message only after the correct submission/payment state.
If it fails
Fix trigger, condition, recipient, or field allowlist and repeat the test.
Save as evidence
Recipient matrix, message ID/log, and redacted received email.
Reconcile any live exception without recharging the customer.
Healthy result
The existing gateway and submission records determine whether payment succeeded, failed, or remains unknown.
If it fails
Pause fulfillment or duplicate collection until the provider record and customer communication are resolved.
Save as evidence
Exception row with IDs, amount, status, owner, and resolution.
Frequently asked questions
Questions that change the next step.
Does a Jotform submission prove the payment succeeded?
No. Treat the form submission and payment-provider transaction as separate states and reconcile them by ID, amount, mode, and timestamp.
How should I test Stripe in Jotform?
Jotform documents a test mode and test-card workflow. Use provider-supported test data in a safe form clone rather than making repeated live charges.
Why does a required deposit show as zero?
The product or calculation field may not be mapped into the payment amount, a condition may skip the field, or the chosen path may not select a priced item. A field map reveals the first zero value.
Official documentation reviewed
Primary sources for the checklist.
Platform interfaces and policies change. These official pages are the baseline; account-specific evidence still determines the correct action.
A first pass can remain a compact artifact, or expand into a new clearly priced scope with long-term support when the work needs upkeep, rollout help, or follow-up checks.
Form calculation or condition correction
Gateway reconnection and live acceptance test
Notification, redirect, and exception-handling cleanup
CSV test and exception log
Sample Jotform payment reconciliation pack
A realistic end-to-end test dataset for fields, expected amount, submission, gateway event, notification, exception, and resolution.
Field-to-amount mapping
Submission-to-transaction reconciliation
Success and failure acceptance tests
CSV fileJotform payment reconciliation matrix
A spreadsheet-ready sample using synthetic IDs and no payment credentials.
These examples are anonymized. Names, domains, emails, private screenshots, exact products, and private commercial details are removed or generalized.
Contact
Still stuck with Jotform?
For a small fixed fee, we can take over the evidence review, controllable corrections, validation, and one clearly bounded support handoff. Platform approval is never guaranteed.