---
title: "Stripe Metadata PRO"
description: "Automatically attach the site name and URL, order ID, customer name, and customer email to new WooCommerce and FluentCart transfers."
url: "https://docs.splitpayplugin.com/features/stripe-metadata/"
---
## Overview
The **Stripe Metadata** feature attaches store-order information directly to each platform-owned transfer object in Stripe, whether the order originated in WooCommerce or FluentCart.
When enabled, new Split Pay transfers include fields that the platform can use in Stripe or through the Transfers API for reconciliation and reporting. Connected accounts receive a separate destination-payment object, so this page does not promise that the transfer metadata appears in every connected-account Dashboard.
Stripe allows up to **50 metadata key-value pairs** per transfer, with keys up to 40 characters and values up to 500 characters. Split Pay truncates string values longer than 500 characters before sending; custom keys must still meet Stripe’s other limits.
## Enabling Stripe metadata
To enable metadata on transfers:
Navigate to **Split Pay → Global Transfer Settings** in your WordPress admin.
Scroll to the feature checkboxes below your global transfer rows.
Check **Include Order Details in Stripe Transfer Metadata.**
Include Order Details in Stripe Transfer Metadata
Save your settings.
Once enabled, all future transfers will automatically include the metadata fields described below.
## What metadata is included
When enabled, Split Pay adds these exact metadata keys:
| Metadata Key | Description | Example Value |
| --- | --- | --- |
| `Site Name` | The WordPress site name | `Example Store` |
| `Site Url` | The WordPress site URL | `https://example.com` |
| `Order Id` | The WooCommerce or FluentCart order ID | `1042` |
| `Customer Name` | The customer’s first and last name | `Example Customer` |
| `Customer Email` | The customer’s email address | `customer@example.com` |
WooCommerce transfer legs may also include leg-specific fields such as `product_id`, `transfer_type`, `transfer_percentage_or_amount`, and `account_wise_tax`. Split Pay separately adds `split_pay=1` to every transfer for identification.
**Privacy:** Enabling this option sends the customer name and email address to Stripe as transfer metadata. Review your customer-data requirements before enabling it.
## Viewing metadata in Stripe
A user with access to the platform Stripe account can view the attached metadata:
Log in to [Stripe Dashboard](https://dashboard.stripe.com).
Navigate to **Balance → Transactions** or search for the specific transfer.
Click on a transfer to view its details.
Scroll down to the **Metadata** section to see the order information.
The metadata is also accessible via the [Stripe API](https://docs.stripe.com/api/transfers/object#transfer_object-metadata), making it easy to build custom reporting or reconciliation tools on top of your transfer data.
## Common use cases
* **Vendor reconciliation** — The platform can match each transfer to a specific store order.
* **Accounting & bookkeeping** — Export transfer data from Stripe (including metadata) for bookkeeping and tax reporting.
* **Dispute resolution** — Quickly identify which order a transfer relates to when resolving payment disputes.
* **Custom reporting** — Use the Stripe API to pull transfer metadata and generate custom reports for your marketplace.
Metadata is only attached to **new transfers** created after the feature is enabled. Existing transfers will not be retroactively updated.
## Developer notes
`spp_transfer_metadata` currently runs only for FluentCart transfers. It receives the metadata array, `null` as its second argument, and `'fluentcart'` as its third argument. For WooCommerce, use the leg-specific filters listed in [Developer Filters](../developer-filters/).
```
add_filter( 'spp_transfer_metadata', function( $metadata, $unused_order, $integration ) {
if ( 'fluentcart' === $integration ) {
$metadata['custom_field'] = 'value';
}
return $metadata;
}, 10, 3 );
```
Register the callback with `10, 3` to receive all three arguments.