Exporting Payments from Stripe with WP Full Pay

WP Full Pay does not include a built-in payment export feature. Instead, all payment data is stored directly in your Stripe account and can be exported from the Stripe Dashboard. Custom fields collected by your WP Full Pay forms are automatically saved as metadata on the corresponding Stripe objects, so they are included in your exports without any extra setup.

Overview: Where payment exports live

When a customer submits a WP Full Pay form, the plugin creates a Stripe object — a charge, subscription, or customer — and attaches any custom field values as metadata on that object. Because the data lives in Stripe, you export it using the Stripe Dashboard's built-in export tool, not from within WordPress.

📝 Note: Custom fields you add to your WP Full Pay forms (for example, "Company name" or "Order reference") are automatically saved to Stripe metadata. No additional configuration is required.

Step-by-step: Exporting payments from Stripe

Follow these steps to download a CSV of your payments, including any custom field metadata.

1. Log in to your Stripe Dashboard.
2. In the left-hand navigation, click Transactions.
3. Apply any date range or filter you need to narrow the results.
4. Click the Export button (top-right area of the Transactions page).
5. In the export dialog, choose CSV as the file format.
6. In the Columns section, enable Metadata to include your custom field data in the export.
7. Click Export to download the file.

💡 Tip: Use the date range filter before exporting so your CSV only includes the transactions you need.

Including custom fields in the export

WP Full Pay saves each custom field as a separate metadata key on the Stripe charge or subscription. When you enable Metadata in the Stripe export settings, each metadata key appears as its own column in the downloaded CSV.

For example, if your form includes a field called Order reference, the exported CSV will contain a column named metadata:Order reference (or similar, depending on how Stripe formats the key).

The metadata key names match the Field name values you set in the WP Full Pay form editor. To review or update the field names on a form:

1. In your WordPress admin, go to Full Pay > Forms.
2. Open the form you want to check.
3. Select the Form Fields tab, scroll to the Custom Fields section, and review the Field name for each field.

📝 Note: Metadata is attached to different Stripe objects depending on your form type:

• One-time payment forms → metadata on the Stripe Charge
• Subscription forms → metadata on the Stripe Subscription
• Save card forms → metadata on the Stripe Customer

Export the matching section of the Stripe Dashboard (Payments, Subscriptions, or Customers) to retrieve the relevant data. For more detail on locating metadata by form type, see Where are custom fields on the Stripe dashboard?

Troubleshooting

Metadata columns are missing from the export

• Make sure you enabled the Metadata option in the Stripe export dialog before downloading.
• Confirm that the form's custom fields have Field name values set. Fields without a name may not sync to Stripe correctly.
• Check that the Stripe API keys configured in WP Full Pay are correct and active. Invalid or expired keys can prevent metadata from being written to Stripe. See Configuring the Stripe API keys for help.

The export shows no payments or fewer payments than expected

• Verify that you are in the correct Stripe mode. Payments made while the plugin was set to Test mode are only visible in the Test section of the Stripe Dashboard, not in the live view.
  • To switch modes in Stripe, use the Test mode toggle at the top of the Dashboard.
  • To check which mode WP Full Pay is using, go to Full Pay > Settings > Stripe Account.
• Widen the date range filter in the Stripe export dialog to include the period when the payments were made.

Custom field values are blank in the export

• Ensure that the custom field was present on the form at the time of the payment. Fields added after a transaction was processed will not appear on historical records.
• If the customer left an optional field empty, the metadata value will be blank in the export.