Introduction

The backend of the onboarding process is essentially the same for both flows, and comprised four steps. The advantage of the OAuth2 method is increased security and the elimination of the user/send_confirmation steps.

The onboarding flow steps are:

  1. User creation.
  2. User confirmation.
  3. User WePay account creation.
  4. Completion of the KYC process.

Regardless of the flow you use to onboard your merchants, their ability to receive payments and transfer funds from their WePay account to their bank account (settlements) is limited until the entire process has been completed and all confirmations received and vetted.

test

yoloswag

test

yoloswag

test

yoloswag

test

yoloswag

test

yoloswag


Onboarding Flows

User/Register/ Onboarding Flow

Create A User

The first step in onboarding a merchant is to create a user that represents the merchant. You will use the user/register API create your merchant user. See the /user/register/ developer documentation for more information.

Note: Until the user is confirmed, by clicking the confirmation email link, they will be in a pending state and will have limited abilities. See the Limitations section, below.

User Confirmation

Once a user has been created, they need to confirm their information. You can send them a user confirmation email with a link in it using the user/send_confirmation API. See the /user/send_confirmation developer documentation for more information.

Create An Account

The next step in the process is to create an account into which your merchant received payments from their payees.

Know Your Client (KYC)

The final step is KYC. In this step the merchant’s banking information is collected so that settlements (transfer of funds from the client’s WePay merchant account to their bank account) can be completed.

OAuth Onboarding Flow

The Oauth flow begins by sending the user to the https://www.wepay.com/v2/oauth2/authorize end point uri. The user will see the following dialog where they can enter their information.

When the user registers or logs in to their account and clicks the Grant Access button, a JSON object is passed back to the function you specify in the script ( See OAuth2 Account Creation for more information ). This is used in conjunction with the /oauth2/token call to obtain a a permanent access token. As a part of the process the user is automatically sent the confirmation email, eliminating the need to call the user/send_confirmation API.

Note: Using the OAuth method does not require the /user/send_confirmation call, the email is generated as part of the underlying OAuth process.

Create An Account

Use the token obtained in the previous step to create a payment account on behalf of the merchant using the /account/create API.

Know Your Client (KYC)

The KYC step for this flow is the same as in the /user/register method, above.


Time Limits

Users Pending Confirmation

The user must complete the confirmation process within 90 days of its creation or the temporary token will expire.

Accepting Payments

If the user is not confirmed within 14 days of taking their first payment, subsequent payments are not allowed until the confirmation process is completed.

Settlement Limitations

Settlements (moving funds from the merchant’s WePay account to their bank account) can not occur until the user has completed the KYC process. That process must be completed within 30 days of the receipt of their first payment, if not, the account will be disabled.