Hello. I am looking for a good performer who will do everything in the best way. Please skip this topic if you have no experience in this area or if this is your first time. Let's value each other's time, thank you!
A script needs to be implemented for receiving payments. The script should work based on the p2p mechanism, transferring from card to card. The gateways will need to be discussed closer to the matter, for example, we can work with ipay, portmone, etc.
Tasks:
- selection of gateways for good payment processing and uninterrupted operation;
- everything should be in Ukrainian, the template where the client pays for the purchase, web admin panel, pages for successful/unsuccessful payments, etc.
- web admin panel, where cards for receiving payments are added/removed. There should always be one card in operation until we remove or change it. Everything here should work perfectly, for example, we remove a card and add a new card, but clients who are already in the process of paying to the old card should continue to pay to the old card, and the statistics (which are detailed) should still update the total amount of transactions even for the card that has been removed from operation;
- a config in the script where the login/password for the web admin panel and the panel address can be edited;
- a separate page for statistics of successful payments (without login and password, a regular page), which resets every day at 00:00, and the payment statistics logs do not need to be saved anywhere. This page should have statistics in alphabetical order. For example, the first place is occupied by the card that is currently receiving payments, and the second place is already another card that has been removed from operation, and next to the cards, the total amount of transactions for that card should be updated. The statistics should work perfectly and update each total amount of successful payments for any card. For example, if we removed one card from operation and added another card, but the client is already paying to the old card, then the statistics should update the total amount even for the card that has been removed from operation;
- a line in the config where the address of the statistics can be edited;
- creation/deletion of payment links in the web admin panel. To create a payment link, you need to enter the payment amount, and a payment link is generated. Links should be reusable, they can be paid indefinitely or until we delete them. Links should work based on which card is currently added; if the card for receiving payments is not added, then the link cannot be created. Some important points should be considered, for example, one link is created for 500 hryvnias, one client is already starting to pay to the card that has been removed (he is already on the 3ds of his bank), and the second client is already paying to the card that has just been added; the first client should continue to pay to the old card while the new client pays to the new card. But what to do if links have already been created, but the card for receiving payments is not added in the web admin panel? In this case, the links should take the amount from the last card that was added until a new card is added in the panel.
- pages for successful and unsuccessful payments (templates and where to redirect clients will be discussed);
- a line in the config where the address for successful and unsuccessful payments can be edited;
- a high-quality and beautiful template where the client enters their card details (this is the payment link), and then they are redirected to the 3ds of their bank;
- a high-quality and beautiful template for the web admin panel;
- the script must work exclusively on mobile proxies. If the script makes all payment requests for all clients from one IP, the anti-fraud system of portmone will trigger, resulting in a stream of unsuccessful payments;
- a line in the config where mobile proxies can be edited, ip:port:log:pass and a link to change the ip;
- for the sake of practicality, the script will be created on several gateways. Therefore, the web admin panel should have a function to enable/disable which gateway. There should always be one gateway in operation. It is not allowed for all gateways to be turned off; there should always be one enabled. Also, the most important points should be considered when switching gateways; payment links and mobile proxies should update this information.
However, for example, one client is already on the 3ds of their bank on the gateway that has been turned off (for example, ipay), and the second client has already managed to get onto the new gateway (for example, portmone), then the first client is already paying through the old gateway (since he is already on the 3ds of his bank), while the second client is only on the payment link, so he is already paying through the new gateway.
- payment statistics in Telegram. Yes, we have web statistics, but this is the statistics of the total amount of successful transactions by card, which is updated next to each card. In Telegram, we need to receive notifications for each successful and unsuccessful payment.
- a line in the config where the bot token and chat id can be edited.
I will gladly consider all options regarding budget and deadlines. Thank you all.
Hello. In search of a good performer who will do everything in the best way. Please skip this topic if you have no experience in this area or if this will be your first time. Let's value each other's time, thank you!
A script needs to be implemented for accepting payments. The script should work based on the p2p mechanism, transferring from card to card. The gateways will need to be discussed closer to the matter, for example, we can work with ipay, portmone, etc.
Tasks:
- selection of gateways for good payment processing and uninterrupted operation;
- everything should be in Ukrainian, a template where the client pays for the purchase, web admin panel.
- web admin panel, where cards for accepting payments are added/removed. There should always be one card in operation until we remove or change it. Everything should work perfectly here, for example, we remove a card and add a new card, but clients who are already in the process of paying to the old card should continue to pay to the old card, and the statistics (which are detailed) should update the total amount of transactions even for the card that has been removed from operation;
- a config in the script where the login/password for the web admin panel and the panel address are edited;
- a separate page for statistics of successful payments (without login and password, a regular page), which resets every day at 00:00, logs of statistics do not need to be saved anywhere. This page should have statistics in alphabetical order. For example, the first place is occupied by the card that is currently accepting payments, and the second place is already occupied by another card that has been removed from operation, and next to the cards, the total amount of transactions for that card should be updated. The statistics should work perfectly and update each total amount of successful payments for any card. For example, we removed one card from operation and added another card, but the client is already paying to the old card, so the statistics should update the total amount even for the card that has been removed from operation;
- a line in the config where the address of the statistics is edited;
- creation/deletion of payment links in the web admin panel. To create a payment link, you need to enter the payment amount, and a payment link is generated. Links should be reusable, they can be paid indefinitely or until we delete them. Links should work based on which card is currently added; if no card for accepting payments is added, the link cannot be created. Some important points should be considered, for example, one link is created for 500 hryvnias, one client is already starting to pay to the card that has been removed (he is already on the 3ds of his bank), and the second client is already paying to the card that has just been added, the first client should continue to pay to the old card while the new client pays to the new card. But what to do if links have already been created, but the card for accepting payments is not added in the web admin panel, then the links should take the amount from the last card that was added until a new card is added in the panel.
- a line in the config where the addresses for successful, unsuccessful payments, and the 404 page are edited;
- a quality and beautiful template where the client enters their card details (this is the payment link), and then they are redirected to the 3ds of their bank;
- a quality and beautiful template for the web admin panel;
- the script must work exclusively on mobile proxies. If the script makes all payment requests for all clients from one IP, the anti-fraud system of the same portmone will trigger, resulting in a stream of unsuccessful payments;
- a line in the config where mobile proxies, ip:port:log:pass, and the link to change the IP are edited;
- for the sake of practicality, the script will be created on several gateways. Therefore, the web admin panel should have a function to enable/disable which gateway. There should always be one gateway in operation. It is not allowed for all gateways to be turned off; there should always be one enabled. Also, the most important points should be considered when switching gateways; payment links and mobile proxies should update this information. But, for example, one client is already on the 3ds of their bank on the gateway that has been turned off (for example, ipay), and the second client has already managed to get onto the new gateway (for example, portmone), then the first client is already paying through the old gateway (since he is already on the 3ds of his bank), while the second client is only on the payment link, so he is already paying through the new gateway.
- payment statistics in Telegram. Yes, we have web statistics, but this is the statistics of the total amount of successful transactions by card, which is updated next to each card. In Telegram, we need to receive every successful and unsuccessful payment.
- a line in the config where the bot token and chat id are edited.
I will gladly consider all options regarding budget and deadlines. Thank you all.
Log in
or
register,
to view the original
Hello. I am looking for a good performer who will do everything perfectly. Please skip this topic if you have no experience in this area or if this will be your first time. Let's value each other's time, thank you!
A script needs to be implemented for accepting payments. The script should work based on a p2p mechanism, transferring from card to card. The gateways will need to be discussed closer to the task, for example, we can consider ipay, portmone, etc.
Tasks:
- selection of gateways for good payment processing and uninterrupted operation;
- everything should be in Ukrainian, web admin panel, etc.
- a web admin panel where cards for accepting payments can be added/removed. There should always be one card in operation until we remove or change it. Everything here should work perfectly, for example, we remove a card and add a new card, but clients who are already in the process of paying to the old card should continue to pay to the old card, and the statistics (which are detailed) should update the total amount of transactions even for the card that has been removed from operation;
- a config in the script where the login/password for the web admin panel and the panel address can be edited;
- a separate page for statistics of successful payments (without login and password, a regular page), which resets every day at 00:00, and the payment statistics logs do not need to be saved anywhere. This page should have statistics in alphabetical order. For example, the first place is occupied by the card that is currently accepting payments, and the second place is already occupied by another card that has been removed from operation, and next to the cards, the total amount of transactions for that card should be updated. The statistics should work perfectly and update each total amount of successful payments for any card. For example, if we remove one card from operation and add another card, but the client pays to the old card, then the statistics should update the total amount even for the card that has been removed from operation;
- a line in the config where the address of the statistics can be edited;
- creation/deletion of payment links in the web admin panel. To create a payment link, you need to enter the payment amount, and a payment link will be generated. The links should be reusable, they can be paid indefinitely or until we delete them. The links should work based on which card is currently added; if no card for accepting payments is added, then the link cannot be created. Some important points should be considered, for example, one link is created for 500 hryvnias, one client is already starting to pay to the card that has been removed (he is already on the 3ds of his bank), and the second client is already paying to the card that has just been added; the first client should continue to pay to the old card while the new client pays to the new card. But what to do if the links have already been created, but the card for accepting payments is not added in the web admin panel? In this case, the links should take the amount from the last card that was added until a new card is added in the panel.
- a line in the config where the addresses for successful, unsuccessful payments, and the 404 page can be edited;
- a quality and beautiful template for the web admin panel;
- the script should work exclusively on mobile proxies. If the script makes all payment requests for all clients from one IP, the anti-fraud system of portmone will trigger, resulting in a stream of unsuccessful payments;
- a line in the config where mobile proxies can be edited, ip:port:log:pass and a link to change the IP;
- for practicality, the script will be created on several gateways. Therefore, the web admin panel should have a function to enable/disable which gateway. There should always be one gateway in operation. It is not allowed for all gateways to be turned off; there should always be one enabled. Also, the most important points should be considered when switching gateways; payment links and mobile proxies should update this information. For example, one client is already on the 3ds of his bank on the gateway that has been turned off (for example, ipay), and the second client has already managed to get onto the new gateway (for example, portmone), then the first client is already paying through the old gateway (since he is already on the 3ds of his bank), while the second client is only on the payment link, so he is already paying through the new gateway.
- payment statistics in Telegram. Yes, we have web statistics, but this is the statistics of the total amount of successful transactions by card, which is updated next to each card. In Telegram, we need to receive every successful and unsuccessful payment.
- a line in the config where the bot token and chat id can be edited;
- a Luna algorithm on the page where the client enters his card details and then is redirected to the 3ds of his bank.
I will gladly consider all options regarding budget and deadlines. Thank you all.
Log in
or
register,
to view the original
Hello. In search of a good performer who will do everything in the best way. Please skip this topic if you have no experience in this area or if this will be your first time. Let's value each other's time, thank you!
A script needs to be implemented for accepting payments. The script should work based on the p2p mechanism, transferring from card to card. The gateways will need to be discussed closer to the matter, for example, we can take ipay, portmone, etc.
Tasks:
- selection of gateways for good payment processing and uninterrupted operation;
- everything should be in Ukrainian, web admin panel, etc.
- web admin panel, where cards for accepting payments are added/removed. There should always be one card in operation until we remove or change it. Everything should work perfectly here, for example, we remove a card and add a new card, but clients who are already in the process of paying to the old card should continue to pay to the old card, and the statistics (which are detailed) should update the total amount of transactions even for the card that has been removed from operation;
- a config in the script where the login/password for the web admin panel and the panel address are edited;
- a separate page for statistics of successful payments (without login and password, a regular page), which resets every day at 00:00, and the payment statistics logs do not need to be saved anywhere. This page should have statistics in alphabetical order. For example, the card that is currently accepting payments is in the first place, and the second place is already occupied by another card that has been removed from operation, and next to the cards, the total amount of transactions for that card should be updated. The statistics should work perfectly and update each total amount of successful payments for any card. For example, we removed one card from operation and added another card, but the client is already paying to the old card, so the statistics should update the total amount even for the card that has been removed from operation;
- a line in the config where the address of the statistics is edited;
- creation/deletion of payment links in the web admin panel. To create a payment link, you need to enter the payment amount, and a payment link is generated. Links should be reusable, they can be paid indefinitely or until we delete them. Links should work based on which card is currently added; if no card for accepting payments is added, then a link cannot be created. Some important points should be considered, for example, one link is created for 500 hryvnias, one client is already starting to pay to the card that has been removed (he is already on the 3ds of his bank), and the second client is already paying to the card that has just been added, the first client should continue to pay to the old card while the new client pays to the new card. But what to do if links have already been created, but the card for accepting payments is not added in the web admin panel, then the links should take the amount from the last card that was added until a new card is added in the panel.
- a line in the config where the addresses for successful, unsuccessful payments, and the 404 page are edited;
- a quality and beautiful template for the web admin panel;
- the script must work exclusively on mobile proxies. If the script makes all payment requests for all clients from one IP, the anti-fraud system of the same portmone will trigger, resulting in a stream of unsuccessful payments;
- a line in the config where mobile proxies are edited, ip:port:log:pass and a link to change the IP;
- for the sake of feasibility, the script will be created on several gateways. Therefore, the web admin panel should have a function to enable/disable which gateway. There should always be one gateway in operation. It is not allowed for all gateways to be turned off; there should always be one enabled. Also, the most important points should be considered when switching gateways; payment links and mobile proxies should update this information. But, for example, one client is already on the 3ds of his bank on the gateway that has been turned off (for example, ipay), and the second client has already managed to get onto the new gateway (for example, portmone), then the first client is already paying through the old gateway (since he is already on the 3ds of his bank), while the second client is only on the payment link, so he is already paying through the new gateway.
- payment statistics in Telegram. Yes, we have web statistics, but this is the statistics of the total amount of successful transactions by card, which is updated next to each card. In Telegram, we need to receive every successful and unsuccessful payment.
- a line in the config where the bot token and chat id are edited;
I will gladly consider all options regarding budget and deadlines. Thank you all.
Log in
or
register,
to view the original
