Test in sandbox

Use case scenario: Update an account that previously completed KYC verification with incorrect merchant name or business information.

Simulation code: The business_name in the patch must be DECLINED.

Use case: Update a sole proprietor account that has already completed KYC verification with an incorrect primary authorized name.

Simulation code: 

• The given_name for the primary authorized user (individual_owners) must contain the word "DECLINED" (e.g., DECLINEDDAVID).
• The surname for the primary authorized user (individual_owners) must be "DECLINED".

Use case scenario: Update a merchant account with an incorrect beneficial owner name.

Simulation code: The given_name and surname for the beneficial owner (office_bearers or beneficial_owners) must be "DECLINED".

Use case scenario: Update a merchant account with incorrect beneficial owner or office bearer address.

Simulation code: For stakeholders (office_bearers or beneficial_owners):

• address_line_1 must be Campus 611
• address_line_2 must be 300
• admin_area_2 must be 300

Use case scenario: Update a merchant account with an incorrect business name and beneficial owner name.

Simulation code:

• The business_name must be "DECLINED".
• The given_name and surname for the beneficial owner (office_bearers or beneficial_owners) must be "DECLINED".

Use case scenario: Update a merchant account with an incorrect beneficial owner address, incorrect primary authorized user information, and missing primary authorized user information.

Simulation code:

• The given_name for the primary authorized user (individual_owners) must contain the word "DECLINED".
• The given_name and surname for the beneficial owner(office_bearers or beneficial_owners) must be "DECLINED".
• Do not include a required data point for a primary authorized user. In this example, we exclude the date of birth.

Use case scenario: Update a key value on the merchant account and trigger a re-verification failure. The system will apply a limitation after 30 days.

You don't have to wait 30 days to verify the limitation. Instead, you can complete the following steps to advance all the limitation counters on a merchant account:

• Use the PATCH API with an add operation and a single email object.

• Use this specific format for the email address you use for the PATCH request, paypaltimetravel.x@domain.com where x represents the number of days you want to simulate. For example, if you want to simulate 30 days passing, you would set x = 30. The email should end with a valid domain.

When processed, the PATCH request advances the counter, but the email address is not stored and does not affect the account.

Simulation code:

• Create a sole proprietor account using keywords that fail verification.
• Edit the account with keywords that trigger a failed re-verification. For example, change the given name of the primary authorized user (individual_owners) to DECLINEDDAVID and the surname to DECLINED.
• After PayPal creates the merchant account and sends webhooks about the status change, complet a GET request to confirm that a limitation is placed on the account. Now, use the PATCH API to add the email address paypaltimetravel.30@paypal.com to the account.

Note: Do not combine the passage of time simulation with other operations in the same PATCH request. For example, you cannot add an email address and phone number in the same request.