...
Your business trading name, which must correspond with:
the name that will appear on cardholder statements (you must state on your website what name will appear on cardholder statements)
the name advised on the payment record.
If the name of your website is different to your business trading name, it is especially important that your business trading name is prominently displayed so the cardholder can readily identify you as both the merchant and the name that will appear on cardholder statements.
Your legal business name (if this differs to your business trading name).
The physical address (including the country) of your approved place of business. A merchant that primarily operates from a personal residence must include the city, state/province, and country of its Permanent Establishment, but is not required to provide the residence address.
Your business and customer service contact details must include a telephone number or email address for customer queries, along with a secondary contact detail of the following:
facsimile number(s)
social media, such as Facebook, Twitter, lnstagram
chatbot/chat box
A complete description of the goods and services available for purchase on your website with the price clearly stated.
Details of your return/refund policies, cancellation policies, and other purchase terms and conditions, and a confirmation of acceptance of the terms and conditions upon customers' purchases. This can be achieved through either:
A 'click to accept' (or other acknowledgement) button, checkbox, or location for an electronic signature in the sequence of final pages before checkout.
A statement that confirmation of acceptance of terms and conditions is implied by submission of the order on the checkout screen near the 'submit' button.
Details of your delivery times for goods and services, which are to be appropriate for your type of business. (If delivery is to be delayed, the cardholder must be notified of the delay and an option provided to obtain a refund).
If applicable, details of any export restrictions and legal restrictions.
Payment Choice - provide the customer with a clear choice of payment brands. Visa, MasterCard, and/or UnionPay full color logos (of equal size) to indicate card acceptance and credential on file.
Credential on file is account information (including, but not limited to, an Account Number or Payment Token) that is stored by a merchant or its agent to process future transactions for a cardholder with cardholder consent. A merchant must display on the payment screen and all screens that show account information both:
The last 4 digits of the account number or token
The Card Schemes logo in full color
Card Security Code (CVV2/CVC2/CVN2) - the payment page of your website must obtain the customer's card security code value for verification. For information security purposes merchants are prohibited from storing the Card Security Code.
Information Security - outline your site's security capabilities e.g. how card payment information is protected.
Secure your page from potential miss use, by using Re-Captcha or similar, this will mitigate any unauthorised transaction attempts. Please Note if payment page is not behind a login, 2FA or is not a one time link, Re-Captcha is strongly advised.
To further improve your security please talk to your account manager about implementing 3D Secure or Kount, both available as part of the Payrix Software suite.
...
Ensure that all terms and conditions are clear and concise. Before a sale is conducted, you must clearly communicate any special restrictions to cardholders.
...
Payment page requirements - Payer Paid transaction fees
For Partners integrating their software to Payrix and are accepting payments via a non-Payrix Hosted Payment Page, your payment page will require the following to ensure it is compliant:
Any fees charged must be clearly displayed in dollar amounts on the payment page, the Direct Debit Request agreement (if offered) and the invoice. This ensure that the payer is fully aware of the fees associated with the transaction and protect the merchants from any disputes regarding the amount charged.
A sample of what the payment page could look like depending on the specific payment methods you are accepting are below:
Sample 1
In this example, the purchase amount is $5.00 and the transaction fees are displayed to the payer so they are aware of fees that are charged for the type of payment.
The total amount charged including the fees will need to be displayed on the next page the payer is directed to. The total amount charged including fees is returned via API if the payment is successful.
Sample 2
In this example, your software is calculating the total transaction fees on the initial payment page and the total charges is split into 3 parts
Goods or Services purchased
Additional fees
Total charged (sum of the above 2)
Should you have any questions around the payment page requirements, you can contact your Partner manager and we will provide guidance around the payment page requirements.
...