Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Test data: uniqueness requirements

The system applies uniqueness checks to several fields when an onboarding application reaches the boarding layer. These checks apply in Sandbox as well as Production. Reusing the same values across test applications is the most common cause of unexpected rejections during integration testing.

Use this page to generate test data that stays unique across repeated and parallel test runs.

Fields that must be unique

Field
Where it is sent
What to do

Signer email

signerEmail (short application) or the stakeholder marked isApplicationSigner: true (full application)

Use a new address for every test application.

Business name

merchantName (short application) or the legal business name in merchantData (full application)

Use a distinct registered business name for every test application.

Signer name

signerFirstName and signerLastName (short application) or the signer stakeholder (full application)

Vary the name for every test application.

Merchant identifiers

partnerMid and partnerExternalId

Use a unique value for every test application.

Reusing business names or signer names across many applications can trigger duplicate checks at the boarding layer, even when the email address is new.

Signer email

The signer receives a real email, so use an address you can access. The recommended approach is plus addressing with a timestamp tag. Most mail providers deliver name+tag@domain to the name@domain inbox.

qa+20260127143015@yourcompany.com

Build the tag from YYYYMMDDHHMMSS so every value is unique and sorts in the order the tests ran.

Parallel test runs

If several tests can start in the same second, add a run identifier or counter after the timestamp so two runs never produce the same address.

qa+20260127143015r1@yourcompany.com
qa+20260127143015r2@yourcompany.com

If plus addressed emails do not arrive

  • Confirm your mail provider or security gateway does not block or strip tagged addresses.

  • Check spam and quarantine folders.

  • If tagged addresses are blocked, use a catch all mailbox on a domain you control, or create a distinct mailbox per test.

Business name

Use a distinct registered business name for every test application. A simple approach is to append a numeric suffix or short identifier to a base name.

Avoid reusing the exact same business name across applications, even across different test runs.

Signer name

Use a varied signer name for every test application. A lightweight approach is to keep a fixed first name and add a sequence number or short random suffix to the last name.

The signer name does not need to be a real person's name, but it should be unique per application.

Merchant identifiers

Use a unique partnerMid and, where you send it, partnerExternalId for every test application. Matching the sequence number you use in the business name makes test records easy to correlate.

Putting it together

The short application example below follows every pattern on this page.

This is an abbreviated example that omits feeInformation. See Sample Payload for complete request bodies.

Troubleshooting a rejected application

If an application is rejected and you are running repeated tests, check that:

  • the signer email has not been used on an earlier test application

  • the business name is distinct from previous test applications

  • the signer name has not been reused across many applications

  • partnerMid and partnerExternalId are unique

If the values are unique and the application is still rejected, contact your Bead team with the applicationId.

Last updated