Once you receive the “signing” webhook, it’s time for the merchant to electronically sign the Merchant Services Account Agreement. This is the document that discloses all account fees, terms, and conditions, and enables Gravity Payments to underwrite the new account.
In order for the business owner to sign, a URL to a DocuSign page is provided in the webhook. This page presents the document, pre-filled with all their account information, in DocuSign’s interface, allowing the user to complete their e-signing.
The DocuSign interface is responsive for desktop and mobile. You can route your user to it directly (no iframe) and they will be returned to your Return URL at the end of signing.
Aside from the business information that’s required for the Account Object (detailed above), there is some documentation that the merchant must provide at e-signing. Embedded in the DocuSign envelope are two required attachment fields. These fields prompt the user to attach the following:
- A current business license
- A voided check from the bank account specified in the Account Object
In addition, there are three optional attachment fields for:
- Processing statements
- Location/Storefront photo
- Marketing materials
The business license and voided check are required documentation for underwriting the new merchant account. The other documentation fields, while optional, can help support the new account’s approval.
If less than 80% of a merchant’s card sales are processed as “swiped” transactions—that is, more than 20% of the total volume indicated in the
acceptanceMethods of the Account Object fall under “keyed”, “moto”, and “internet”—then the account is considered to be a “MOTO” account. MOTO is a legacy term meaning “Mail Order / Telephone Order”, which today signifies that a significant portion of sales are not accepted by physically swiping, tapping, or dipping the payment card.
For MOTO accounts, there is an addendum page included with the Merchant Services Account Agreement (for non-MOTO accounts, this page does not appear). This addendum contains a number of required questions which must be completed and e-signed, as shown below:
Preparing the User
As a matter of UX best practice, and to avoid user frustration or abandonment, it is highly advised to provide the user a list of “Things You’ll Need” as they begin the signup process for a merchant services account. This list should include any of the business information items for the Account Object that you don’t already have on record, as well as the documentation items required during e-signing. Since several of these items may require some time for the user to retrieve, it’s important to provide this list upfront and allow the user to return to the signup when they’ve collected the required items.
Similarly, since the user completing the signup may not be the owner, or there may be two owners required to e-sign, it might be best to inform the user upfront of the e-signature requirement and of the mechanism by which your app will handle it. For instance, a contextually-placed message to the effect of saying “this owner will be sent an invitation by email to complete their e-signing” could make the matter clear before confusion or ambiguity sets in.
If products are ordered with the account request, they will be detailed in an order form page at e-signing (if no products are ordered, this page will not appear). The user will see a line item for each product showing quantity and price. Point-of-Sale systems will show license and monthly fees if applicable. Gateways will show setup, monthly, and per transaction fees if any. The prices and fees displayed on the order form will be debited from the merchant’s bank account on a one-time or recurring basis as appropriate.