Using white-label setups, Partners can customize the Payrix Pro Portal and various platform features to reflect their company name, branding, and URL. This approach ensures that your merchants benefit from a completely branded user experience, removing any perception that they are accessing a third-party platform when using Payrix Pro.
White Label Setup
As part of the white label setup, Partners receive a CSV file containing the required CNAME records to be added to their DNS host registrar:
Email authentication: Three of the CNAME records are Amazon DKIM entries, which enable Payrix Pro to send emails on the Partner’s behalf using the designated outgoing email address.
Custom domains: Two additional CNAME records are used to configure the API and Portal subdomains, ensuring that the Partner’s environment is fully branded and accessible under their own domain structure.
White Label Intake Form Requirements
The White Label Intake form requires some basic information about the company, owner, and business entity, along with the following:
White Label Name: The name that appears in the header and footer of your portal.
API Subdomain: A domain that your company owns, used to redirect to the Payrix Pro API. For example: “api.yourcompany.com”.
Portal Subdomain: A domain that your company owns, used to redirect to your white-labeled Payrix Pro production environment portal. For example: “portal.yourcompany.com”.
Outgoing Email: The email address used as the “From” address shown on emails from your platform to your Merchants such as boarding notifications or requests. For example: “notifications-noreply@yourcompany.com”.
Invoicing Email: The email address used as the “From” address shown on invoices sent from your platform to Merchants. For example: “billing@yourcompany.com”.
Attachment: A file upload prompt to provide your various logos in PNG or JPEG formats:
Sandbox Portal Subdomain
The sandbox environment portal will utilize a subdomain derived from your provided production subdomains for the portal and API. To clearly distinguish this environment, a test- prefix will be automatically added to the beginning of each subdomain. For example:
“api.yourcompany.com” in sandbox becomes “test-api.yourcompany.com”
“portal.yourcompany.com” in sandbox becomes “test-portal.yourcompany.com”
Logo Type | Description | Size Requirements |
|---|---|---|
Main | The logo that displays in the header of your portal. | 275 x 80 px |
PayFrame | The logo displayed on hosted payment page headers when sent to customers. | 60 x 60 px |
The logo displayed on your outgoing platform communication emails. | Maximum height of 140 px | |
Favicon | The favicon icon displayed in your users' browser tabs, browser history, toolbar apps, and bookmarks dropdowns. | 32 x 32 px |
Once you submit this information, an implementation specialist will apply your requested branding or contact you if more information is needed.
White Label Setup FAQs
Here is a list of frequently asked questions regarding white-label setups:
Why do I need to submit the business and owner information for this setup?
A: The company's legal name and email address are risk requirements of the Payrix Pro platform.
Can multi-level subdomains be used?
A: Yes, multi-level subdomains are permitted. For example: https://your.shop.example.com.
How should logo attachments be uploaded?
A: Please upload your logo attachments in a White Label Intake Request using the Attachments field.
For the best experience, use logos with a transparent background (preferably a PNG), as the white-label setup features a grey background. Non-transparent logos may not look good on the Merchant-facing portal.
What are the graphic size requirements for logos?
A: The four graphic size requirements are listed below:
Main: 275 x 80 px
PayFrame: 60 x 60 px
Email: Maximum height of 140 px
Favicon: 32 x 32 px