Step-by-step guide for setting up your Ardley Offers domain and white-labeled email addresses.
Lower environment setup
Ardley is responsible for setting up all lower environments necessary for the development build. No customer input is needed for these steps.
SFTP Setup
SFTP is the preferred method for delivering the customer data file containing borrower records and data used to generate offers. In order to set this up Ardley will coordinate with your IT group on the following steps:
- Public key for the SFTP
- Username for the SFTP
- Customer IT verifies the connection
Email Setup
There are two email addresses requires for setup:
- Promotional
- This is the email that is used to send offers to the borrowers
- Example email address: CustomerService@institution-domain.com
- Transactional
- This is the email sent to the borrower once they've engaged with an offer
- eg: When the borrower needs to verify or when the borrower has submitted an application successfully
- Example email address: CustomerSupport@institution-domain.com
Steps to setup and white-label preferred email addresses:
- Customer needs to install three (3) DNS entries provided by Ardley
- Ardley needs to verify DNS entry, email deliverability, and will send a verification email to customer
- Customer must click the verify email link to complete the setup
SPF & DMARC Records
If DMARC is configured on your DNS server, include amazonses.com is in your SPF record:
v=spf1 include:amazonses.com ~all
Domain Setup
Ardley will host the offer campaign experience at a domain set by the customer. This domain is typically a sub-domain of the customer's existing primary website domain, eg: offers.insititution-domain.com.
To complete the DNS setup for the preferred domain name, the following steps are required:
- Customer needs to install three (3) DNS entries provided by Ardley
- This allows Ardley to take ownership of the SSL certificate and host the application
- Ardley needs to verify the installed DNS entries through our services
- After completing the setup for the Production infrastructure, Ardley will then provide two (2) additional DNS entries
- The first redirects traffic to the white-labeled API
- The second redirects traffic to the application API
- These additional DNS entries will need to be verified through Ardley's services