The Solidgate Payment Form is designed for seamless user interaction, providing extensive customization and validation features.
Additional fields
The Solidgate Payment Form will check the Card BIN and receive a list of necessary additional fields according to information about the BIN country (the first six digits).
Also, depending on the provider, the customer phone parameter is often used to verify the identity of the person making a payment; for example, in India, this is indian_customer_phone . This parameter typically requires the person to enter their registered mobile phone number, which is then used to authenticate the payment.
Styling additional fields
Additional fields classes will be formed as follows:
|
|
You can customize all additional fields at once using the additional_field class. In this case, styles will be applied to all additional field classes described in the table above.
|
|
If you want to customize a specific field, you need to apply styles to this specific additional field class name.
|
|
Validation rules
Front-end validation and auto-tabulation prevent errors and fraud, verify data correctness, enhance user experience, end increase transaction success.
Card number
- Validate the correctness of data entered (check data entered for validity)
The validity of the card number is verified by the Luhn Algorithm. The Luhn Algorithm calculates the check digits of a plastic card number in accordance with the standard ISO/IEC 7812 WIKI
- Define card brand to display the desired logo
For card payments, one of the most important UX rules is automatic card type detection and automatic card number formatting (spacing). To implement these functions, you need to know the IIN ranges and spacing patterns for card types.
- Determine the country of the card by BIN and add fields dynamically if necessary
To dynamically add fields to the form, we need to define the country of the card brand. Depending on this, we add the required field on the frontend.




Expiry date
- The expiration date field accepts dates in both of the following formats: MM/YY, MM/YYYY
- The date entered should be in the future
CVV
The CVV field can only accept 3 or 4 digits. Validation of the CVV field depends on the card brand:
- for AMERICAN EXPRESS, the CVV field must contain 4 digits
- for all other card brands, the CVV field must contain 3 digits
Cardholder
The field with the name of the cardholder is disabled by default. It is possible to enable this field through CSS styles.
- Rules for the field
- at least 3 characters
- convert from Cyrillic to Latin
- must not contain symbols and numbers, only letters
- auto tabulation is disabled
The card_holder
field is specifically required for transactions from certain countries.
Supported countries include Argentina (ARG
), Bangladesh (BGD
), Bolivia (BOL
), Brazil (BRA
), Cameroon (CMR
), Chile (CHL
), China (CHN
), Colombia (COL
), Costa Rica (CRI
), Dominican Republic (DOM
), Ecuador (ECU
), Egypt (EGY
), El Salvador (SLV
), Ghana (GHA
), Guatemala (GTM
), India (IND
), Indonesia (IDN
), Japan (JPN
), Kenya (KEN
), Malaysia (MYS
), Mexico (MEX
), Morocco (MAR
), Nigeria (NGA
), Panama (PAN
), Paraguay (PRY
), Peru (PER
), Philippines (PHL
), Senegal (SEN
), South Africa (ZAF
), Tanzania (TZA
), Thailand (THA
), Turkey (TUR
), Uganda (UGA
), Uruguay (URY
), and Vietnam (VNM
).
Supported browsers
- some of the user’s extensions can break the correct behavior of our payment form
- we don’t guarantee payment form stable functioning when rendered inside in-app browsers (Facebook, Instagram browser, etc.)
The Solidgate payment form (JS) strives to support the latest versions of all major browsers. For security reasons and to provide customization options to customers, we do not support browsers that do not receive security updates and are low usage.
Our support extends to the following browsers:
- Chrome, Chrome Mobile, Firefox, Samsung Browser, Opera and Microsoft Edge
- Safari on desktop and iOS
Supported translations
The Solidgate Payment Form is translated automatically by detecting the location of the customer’s browser.
Afrikaans | af |
Arabic | ar |
Bengali | bn |
Chinese | zh |
Czech | cs |
Danish | da |
Dutch | nl |
English | en |
Finnish | fi |
French | fr |
German | de |
Hindi | hi |
Indonesian | id |
Italian | it |
Japanese | ja |
Korean | ko |
Malay | ms |
Norwegian | no |
Polish | pl |
Portuguese | pt |
Romanian | ro |
Russian | ru |
Spanish | es |
Swedish | sv |
Thai | th |
Turkish | tr |
Ukrainian | uk |
Vietnamese | vi |
Localization can also be configured by passing a subset of
IETF language tags
WIKI
by passing in into PaymentIntent
Begin by setting up your backend, a vital step for successful implementation.
object
.
en
by default.
If you have any questions or require assistance, please do not hesitate to contact our support team.