Skip to main content
Stripe data merge

Stripe data merge streamlines workflows by enabling customers to map and transfer information from PandaDoc directly into Stripe.

Updated over a month ago

Availability: All plans

Stripe data merge streamlines workflows by enabling customers to map and transfer information from PandaDoc directly into Stripe. Whether it’s customer details, payment specifics, or custom variables, this feature ensures that all relevant data is accurately transferred, reducing manual work.

Skip to:

Customer record matching

You can search for and match records using any variable or field in the document, helping to avoid the creation of duplicate customer records.

To start, open your template or document, and navigate to the Payment section.

Then choose Advanced options > Data merge to set up mapping rules.

Select the criteria for mapping payer data to verify if a customer already exists in Stripe. To do this, link a PandaDoc variable or text field ID on the left to a corresponding Stripe field on the right. PandaDoc will then automatically check if the linked variable/text field matches the Stripe field value whenever the payment is initiated.

Note: If no existing customer record is found based on the selected criteria, or if no criteria are chosen, a new customer record will be created in Stripe.

How to map data Customer object

Next, map PandaDoc text fields, variables, or payment app data on the right to the Stripe fields on the left for the Customer object in Stripe.

Important:

Make sure to select ‘Don’t overwrite existing Stripe fields’ to prevent populated fields in matched Stripe customer records from being updated with PandaDoc data.

Default values for the fields will be automatically pre-selected. To change the selected PandaDoc variables, simply click the 'x' button to remove the preselected ones, then choose the desired variable or text ID from the dropdown on the right to map to the corresponding Stripe field.

If you only need to map data to the Customer object in Stripe, remove the unnecessary fields from the PaymentIntent object by clicking the bin icon on the right side of the field line.

You can use role, system, custom, and payment app variable values to update Stripe fields.

Note: You can map as many PandaDoc fields as you need to the Name and Description fields in Stripe.

When you send the document with the configured mapping rules, the Customer fields in Stripe will be updated with the data from the PandaDoc document as soon as the payer selects Continue to payment to initiate the payment.

How to map data to PaymentIntent object

In the mapping rules set up, scroll down to the PaymentIntent/Payments object to map the desired PandaDoc text fields, variables, or payment app data on the right to the Stripe fields on the left.

Note: You can map as many PandaDoc fields as you need to the Name and Description fields in Stripe.

To add more Stripe fields to map data to, select +Add Stripe fields, select the fields where you need to map PandaDoc data, and select Apply.

If you only need to map data to the Payment object in Stripe, remove the unnecessary fields from the Customer object by clicking the bin icon on the right side of the field line.

Stripe fields that you can update with PandaDoc data

  • Name

  • Email

  • Phone

  • Description

  • Receipt email

  • Shipping recipient name

  • Shipping phone

  • Shipping carrier

  • Shipping address:Country

  • Shipping address:City

  • Shipping address:Line 1

  • Shipping address:Line 2

  • Shipping address:Postal code

  • Shipping address:State/Region

  • Shipping tracking number

  • Statement descriptor

  • Statement descriptor suffix

  • Metadata

Once you’ve matched needed variables, text field IDs, and payment app data with the Stripe fields select Save to apply the rules.

The Payment Intent fields in Stripe will be updated with data from the PandaDoc document, as soon as the payer selects Continue to payment to initiate the payment.

Did this answer your question?