Pre-Populating Existing Customer Data
Partner Pages and Embeds support pre-populating select fields on the application form, which is useful when you already have that info on hand for that user, or want the front-end to default to particular values.
How to Implement Pre-pop Fields (for Either Hosted Integration Type)
Regardless of the implementation type (Partner Page vs Embed), we support pre-pop for certain non-PII fields to decrease UX friction and increase app submit rates. Fields can be pre-populated by adding query parameters to the respective URL in the below format*:
Where to Place Pre-pop Fields (Different by Hosted Integration Type)
As an example, you may want to pre-populate the application with a requested Loan Amount of $10,000 and Credit Rating of "excellent". You may do so by appending ?app.loanAmount=10000&app.providedCreditRating=excellent to your Partner Page or Embed:
Partner Page
To pre-populate fields in a Partner Page, append the parameters to the end of the URL path as follows:
Embed
To pre-populate fields in an Embed, use the following syntax in the tags attribute on the opening moneylion-lending-search tag as follows:
Supported Client Tag Keys
The following is a list of params that can be added to the URL:
Loan Purpose
app.purpose
Requested Loan Amount
app.loanAmount
No dollar signs, e.g. '6000'
Credit Rating
app.providedCreditRating
City*
app.city
Spaces should be converted to '%20', e.g. 'New%20York'
State*
app.state
Zip Code*
app.zipcode
Either 5 digits, or 9 digits separated by hyphen (5+4)
Property Status
app.propertyStatus
Date of Birth
app.dateOfBirth
Format: mm/dd/yyyy, e.g. '01/01/1990'
Highest Level of Education
app.educationLevel
Employment Status
app.employmentStatus
Annual Income
app.annualIncome
No dollar signs, e.g. '100000'
Pay Frequency
app.employmentPayFrequency
*These fields will be overwritten if the user’s location is detected
Last updated
Was this helpful?
