Edit shop details and settings
To edit the shop details indicated during the shop registration, follow these steps:
- Go to Account Manager >
- Go to the line of the shop in the If required, use Search for a merchant’s shop.
- Click Edit or click View and then on the shop setting page click
- Change the shop settings and details, as described in the table
- Click Apply to save your changes or cancel
Table: Shop setting parameters
|
Parameter |
Description |
Notes |
|
Name * |
The shop brand name. |
|
|
Business category |
The business category of the shop. |
For more information, see Business categories. |
|
URL |
The URL of the company or the shop. |
Start with https://. |
|
Contact e-mail * |
The shop contact email. |
Shown in transaction receipts. |
|
Contact phone * |
The shop contact phone. |
Shown in transaction receipts. |
|
Notify customer about transactions |
The option to notify customer about transactions. |
Notifications are sent out to customer emails, if they are indicated upon payment. |
|
Send webhook notification to PSP |
The option to send webhook notifications for the shop’s transactions to PSP. |
The webhook notifications will be sent to the URL specified in the PSP settings (when setting up PSP or activating this option for them). |
|
Company name |
The merchant's company name. |
A pre-filled field. |
|
Person, who entered the agreement |
The name of the employee or contact person of the merchant entitled to enter into a contract on behalf of the company. |
|
|
Title |
The position of the employee or contact person entitled to enter into a contract on behalf of the company. |
|
|
Acting on the basis of |
Name, number, date of issue of the document on the basis of which the employee or contact person is entitled to enter into a contract on behalf of the company. |
|
|
Tax Id |
Taxpayer identification number. |
|
|
Legal address |
Legal address of the company (street, house, building, office). |
|
|
Country * |
Country of incorporation of the company. |
|
|
City * |
City of incorporation of the company. |
|
|
Postal code |
Legal address (zip or postal code) of the company. |
|
|
Mailing address |
The mailing address of the company. |
|
|
Bank account details |
Additional bank details. |
|
|
Accountant email |
The accountant’s contact email address. |
|
|
Enabled |
The shop activation status. |
If activated, the merchant can accept payments. Otherwise, all payments will be declined. |
|
Allow to return PAN in token data response |
The option to let the merchant get the card PAN (Personal Account Number) in a response to a request of card details. |
Card PAN can be processed only by PCI DSS certified merchants. The option should be negotiated with acquirers. |
|
Allow host-to-host transactions |
Selecting this checkbox lets the merchant use this shop for sending card number ( credit_card.number ) in the host- to-host requests of the following transaction types: payment, authorization, payout, checkup and P2P transfer. If the permission is not activated and the request contains the card number, the request will result in an error. This permission is not required for sending card tokens ( credit_card.token ) and for sending the card number of the recipient in P2P transfers ( recipient_credit_card.number ). |
By default, the permission is deactivated for the newly created shops. |
|
Send PAN in the transaction verification request |
If selected, the transaction verification request will contain PAN in credit_card.number and recipient_card.number parameters. |
Card PAN can be processed only by PCI DSS certified merchants. The option should be negotiated with acquirers. |
|
Allow to process plain PAN data |
The option to let the merchant accept payments with card PANs (Personal Account Number). |
Card PAN can be processed only by PCI DSS certified merchants. The option should be negotiated with acquirers. |
|
Allow transactions w/o CVC |
The option to let the merchant accept card payments without CVC (Card Verification Code) or CVV (Card Verification Value). |
The option should be negotiated with acquirers. |
|
Permit to disable 3- D Secure for a transaction |
The option to let the merchant process card payments without the 3-D Secure check. |
The option should be negotiated with acquirers. |
|
Use new payment form |
The option to activate the payment form. |
|
|
Enable async payments |
The option to activate the asynchronous mode. |
The asynchronous mode allows the merchant not to hold a connection with the provider while processing payment requests and responses. The merchant can request for a transaction status at any time. |
|
Enable cascading payments |
The option to activate the cascading payments. |
The cascading processing mode makes the system route transactions to those payment gateways and in that order, as specified in the merchant’s request, till the transaction is not processed successfully. |
|
Display save card toggle on payment page |
The option to let customers save the card for payments in the merchant’s shop. |
If the option is activated, the system will display the card number for the customer on the payment widget and will provide the card token to the merchant for recurring payments. |
|
Hide another card toggle on payment page |
The option to hide the toggle to save another card on the payment widget. |
|
|
Allow transactions with decrypted *pays data |
The option to let the merchant process payments with decrypted Apple Pay, Google Pay, Samsung Pay tokens. |
|
|
Use Widget v2 |
The option to activate the widget v 2 for the shop. |
|
|
Use substitution domain |
The option to use a substitution domain while working with the external 3-D Secure MPI. |
The substitution domain is set upon the payment service provider registration and can be used instead of the system’s 3D Secure domain, while the customer is redirected to the ACS - form of the card issuing bank. |
|
Use 3DS v1 API response format |
The option to enable the API 3DS v1 response and flow format while working under 3DS v2. |
The system applies the API 3DS v2 response and flow format by default. |
|
Use Smart Routing to verify P2P transfer |
The option to use Smart Routing for P2P verification requests (verify-p2p and p2p-restrictions). This option is recommeded if there are several gateways used for processing P2P transactions with different commission values depending on the card brand of the sender and/or recipient |
By default, not activated. In this case, the gateway for processing P2P transactions is selected in alphabetical order from the list of gateways suitable for the card brands in the transfer. |
|
Use Smart Check |
The list with the following options:
|
By default, Disabled |
|
Limits currency |
The limit currency used to calculate the limit amounts. |
|
|
Accept tokens from shops |
The option to share card tokens, so that they can be used for payments in other shops of the merchant. |
If the token is shared, the merchant can process a payment by this card token not only in the shop where the original transaction was initiated, but also in the shop that the card token was shared with. |
|
Agent |
The name of the agent of the merchant. |
If you assign an agent to a merchant shop, the system will calculate the agent’s revenue as a percentage or a fixed amount taken for each processed transaction. |
|
Bank account details |
||
|
Bank name |
The name of the bank or financial institution where the merchant's current account is opened. |
|
|
Bank Identifier Code (BIC) |
Bank identification code. |
|
|
International bank account number (IBAN) |
International bank account number. |
|
|
Conditional number of settlement participants |
Conditional number of settlement participants. |
|
|
Country |
The country in which the merchant's current account is opened. |
|
|
State |
The legal address (state) of the bank or financial institution where the merchant's current account is opened. |
|
|
City |
The legal address (city) of the bank or financial institution where the merchant's current account is opened. |
|
|
Postal code |
The postal code of the bank or financial institution where the merchant's current account is opened. |
|
|
Address |
The legal address of the bank or financial institution where the merchant's current account is opened. |
|
|
Widget customization |
||
|
Color of buttons |
Color HEX-code for the widget and payment page buttons. |
By default, the color set by the provider is applicable by default. If required, a merchant can apply own widget customization settings. |
|
Background type |
Widget and payment page background style. Possible values:
|
By default, the background set by the provider is applicable by default. If required, a merchant can apply own widget customization settings. |
|
User Agreement |
||
|
Use the User Agreement |
The option to display User Agreement toggle on the Order confirmation pages that are generated for plans and products. |
The Pay button is deactivated unless the customer clicks the toggle, confirming that they accept the User Agreement. |
|
URL to the User Agreement |
URL to the page with the text of the User Agreement. |
If both URL and file are provided, the text will link to the URL. |
|
Switch text |
Text that will be placed next to the User Agreement toggle. Fill in the field according to the example: I agree to the terms and conditions of [the User Agreement] . In this case, the link will either open the attached file or the provided URL in a separate tab. |
|
|
User Agreement file |
The button for uploading the PDF file with the User Agreement. The file size must not exceed 1 MB. If the file size is bigger, it is recommended to provide a URL to the User Agreement instead. |
If both URL and file are provided, the text will link to the URL. |
|
*required |
||




