This Integration Agreement sets out guidelines and requirements for all integrations
that utilize Aeropay’s software. The requirements listed below have been developed to
ensure that Company understands Aeropay’s expectations. Each requirement contains
a description pertaining to why it exists.
1. Authentication
Company agrees to enforce SMS 2-factor authentication for all users at the time of
registration and when users change their number via Aeropay’s Authentication or
another vendor. If Company does not require any MFA, then Company must build
Aeropay’s passwordless SMS 2FA for each transaction or participate in B2B
transactions where they are not required to enforce MFA.
Why: 2FA is an industry standard for verifying that individuals are in possession of their
personal devices/email accounts. Aeropay utilizes email/SMS 2FA to provide seamless
account verification while mitigating fraud and account takeover.
2. Accurate Merchant/User Management
Company agrees to provide complete and accurate data outputs to the best of their
ability through commercially reasonable procedures. Data transmitted is defined as a
user’s first/last name (or business name), email, and phone number. Company agrees
to make cell-phone numbers unique to the user.
Why: Aeropay’s system will not allow for duplicate accounts to be created so it is
advised that the Company does not as well. This can also prevent bad actors from
creating multiple dummy accounts on Company’s platform.
3. Age & Location Verification
Company agrees to adhere to local age and verification requirements with regards to
the products they sell and services Company provides. For example, cannabis users
must have their IDs verified and gaming users are limited to using apps in certain
States.
Why: State/Federal laws require that companies adhere to these laws in order to operate.
4. Branding
Company agrees to include the Aeropay provided package of brand assets.
Aeropay is a growing network and it is important that Company’s users understand
Aeropay’s involvement in their transactions. As Aeropay’s network grows, we expect
higher conversion on Company’s site as users become familiar with seeing Aeropay’s
brand in different places.
Why: New Open Banking features showcase Aeropay as the connection when linking a
bank on Company’s website. Showing the same logos will eliminate any confusion.
5. Messaging
Company agrees to include the Aeropay provided recommendations on their site. (i.e.
FAQs, marketing)
Why: A few short sentences can go a long way in decreasing the amount of support
requests that are received. We want to optimize any experience we can while thinking a
few steps ahead of each user.
6. Terms of Service & Privacy Policy
Company agrees to include the following excerpts in their Terms of Service and Privacy
Policy:
In Company’s Terms of Service:
“Special provisions related to Bank Transfer Payments
$IntegratorName has partnered with financial services software company Aeropay to
offer you ACH payments. When you create a $IntegratorName Account and connect a
bank to complete ACH payments, you will be creating an Aeropay account. You
authorize $IntegratorName to share your identifying information with Aeropay to open
and support your $IntegratorName Account. You must comply also with Aeropay’s
Terms of Service when creating or using your $IntegratorName Account. The Aeropay
Terms of Service may be modified from time to time, and the governing version is
incorporated by reference into this Terms of Service. Any term not defined in this section
but defined in the Aeropay Terms of Service assumes the meaning as defined in the
Aeropay Terms of Service.”
In Company’s Privacy Policy:
“Data Sharing with Payment Vendors
$IntegratorName has partnered with financial services software company Aeropay to
offer you ACH payments. When you create a $IntegratorName Account and connect a
bank to complete ACH payments, you will be creating an Aeropay account. It is your
responsibility to make sure the data you provide us is accurate and complete. You must
comply also with Aeropay’s privacy policy (the “Aeropay Privacy Policy”) when creating
or using your $IntegratorName Account. The Aeropay Privacy Policy may be modified
from time to time, and the governing version is incorporated by reference into this
Privacy Policy.”
Why: As a legal requirement, Company’s users must be exposed to our terms of service
during their account creation (or enrollment into Aeropay bank transfers). Company
must include links to these with excerpts in their terms of service and privacy policy.
7. Preauth + Refunding/Voiding
If Company intends to collect payments before orders or services are fulfilled, then
Company agrees to utilize Aeropay’s preauthorization functionality and automate the
refunding and voiding of transactions with Aeropay’s API.
Why: Aeropay preauthorization and automated refunds will eliminate the need to go
through and manually perform these actions for canceled or unfulfilled orders/services.
When these manual actions are not completed, users endure an unintended refund
delay of about one week or end up disputing their payments.
8. Suspending
Aeropay will suspend all users with outstanding declined payments and consider
banning them permanently. Company agrees to also suspend these users from
Company’s platform until the Aeropay debt is fully resolved, or follow procedures
otherwise agreed upon to support the use case.
Why: Users may try to pay through alternative payment options when they have
outstanding debts from Aeropay. Users will be advised to resolve these debts to avoid
further penalties and help keep Company or Company’s mutual clients’ decline rates
down.
9. Support Communication
Company agrees to establish efficient channels of communication with Aeropay’s
customer care and payment operations teams. For example, a shared Slack channel or
routine check-in call.
Why: To serve mutual customers, Aeropay needs each team to work together.
Customers may feel disregarded if this mutual communication does not take place and
take it out on each client publicly via reviews or social media.
10. API Versioning
Company agrees to maintain Aeropay’s most up-to-date API versioning.
Why: Aeropay may deprecate endpoints and update their API versioning. It’s important
that Company is utilizing Aeropay’s most current documentation.