Integration of Tpay with a proprietary application

Budget: 1800 PLN Deadline: 4 days

Good morning, I can take care of fixing the Tpay integration in the Base44 application. I estimate the diagnostics and implementation phase at 1800 PLN and about 4 days, provided that there is access to the Tpay panel, webhook logs, and the configuration of pickup points in Base44.

First, I would check the full subscription cycle - the first payment, BLIK alias registration, renewal, webhook from Tpay to the application, and the application's response after a failed attempt. Typically, the problem lies not in the payment itself, but in the mapping of the alias, transaction statuses, or the fact that the application does not distinguish between the first transaction and recurring charges.

Two questions before a precise estimate:
> Does Base44 allow editing of its own server part or only actions and integrations without a full server?
> Are there logs from Tpay for the moment when the subscription expires and the payment is not collected again?

Similar experience:
> https://business.ingello.com/vorfahr - automation and integration of processes with payments and user logic
> https://business.ingello.com/prime-eva - e-commerce, orders, integrations, and data accuracy control
> https://systems-fl.ingello.com - Ingello Systems for projects with architecture, integrations, and automation

If after analysis it turns out that Base44 does not allow proper handling of recurring webhooks, I will propose a small intermediate API module. It can be kept simple, but with payments, it’s better to have a stable mechanism, because whoever pays twice for the same mistake pays the most expensive =) Expand

Budget: 2500 PLN Deadline: 30 days

I will conduct a log inspection and implement proper handling of renewals via the Tpay API (cyclical method using saved cli_auth), without involving the user in re-entering the BLIK code. Simple financial matters — in a private message.

The problem with cyclical BLIK most often arises because, during the next charge attempt (when the subscription expires), the application sends a request as a standard, one-time BLIK instead of using the api/v1/transaction/execute-saved-alias method, or the server does not correctly process the asynchronous notification (Notification URL) from Tpay confirming the registration of the user's alias. Do you currently have the ability to view what exactly Tpay returns in the logs at the moment when the application tries to automatically renew the subscription?

Budget: 2000 PLN Deadline: 7 days

Hello, I worked on integrating Stripe with a mobile app for a fitness studio, where I set up automatic monthly subscription billing with a 95% transaction success rate for 150+ active users.

I’m curious if the issue with webhooks occurs only for BLIK, or do other payment methods also have problems with subscription recovery?

I suggest we connect; I will provide you with free technical consultation and we can create a development plan + I will tell you about my team!

Budget: 2400 PLN Deadline: 5 days

I already have a practically ready similar solution for recurring payments and webhooks, it can be quickly adapted to Tpay and Base44, we can discuss the details here now, I am on the line ))
I estimate the first stage of diagnosis and repair at 2400 PLN and 5 working days.
We can start with a technical audit of the current integration, then improve the BLIK alias registration, Tpay notification handling, and subscription renewal logic.
On the Tpay side, it will be crucial to check whether the application saves the correct alias, responds to the webhook with the required status, and does not lose the user - subscription - payment association.
!!The most important point is the BLIK alias and the renewal webhook!!
- Do you have access to the code or backend settings in Base44 where the webhook is received?
- Are there logs of failed renewals and a sample test subscription on which the error can be safely reproduced?
Similar projects Ingello
- https://business.ingello.com/vorfahr - sales automation and integrations, similar through event and payment logic
- https://business.ingello.com/platforma - platform with processes, roles, and status control, similar through the business part of subscriptions
More about the team and approach to such implementations
https://systems-fl.ingello.com Expand

Budget: 2000 PLN Deadline: 6 days

I understood the task: an application built by Base44 (no-code AI builder), published on Google Play as Strefa Przemienieni. Tpay as the payment gateway, BLIK recurring set up. The first payment goes through correctly, the bank records the recurring payment, but upon subscription renewal, BLIK aliases do not charge the fee — and there is a problem with the webhooks (App↔Tpay).

According to the Tpay pattern and typical errors in BLIK recurring, there are usually three culprits.

First — the webhook from Tpay arrives, but the application either does not confirm it with a status of 200 or uses a different endpoint than registered in the Tpay panel. Tpay checks the response — if the application does not respond with a status of 200 and a correct md5/sha256 signature, Tpay treats the webhook as undelivered and retries several times, then cancels the recurring payment. It is necessary to verify in the Tpay panel the notification URL and the logs of incoming requests on the application side.

Second — the BLIK alias has a limited validity period. In BLIK recurring, after the first transaction, an alias is issued by the client's bank. If the client has not confirmed the recurring consent in the banking application (some banks require active acceptance of recurring after the first payment), the alias is one-time and when attempting to renew, the bank rejects the operation. This needs to be verified on a specific test client — whether in their banking application there is an active recurring consent.

Third — incorrect channel ID or group when calling the next recurring transaction. The first transaction may be initiated from the channel BLIK_TRANSFER, while subsequent recurring ones must go through the channel BLIK_LEVEL_ZERO with the parameter recurrent=1 and the correct client token. If Base44 generates the code without this distinction, all renewing payments will attempt to process as new and fail.

What I plan to do. First — I will log into the Tpay panel and check the webhook logs for the last 14 days, identifying whether notifications are sent out and with what status they return. Second — in the Base44 application, I need to find the part responsible for the webhook handler and check the response code plus signature verification. Third — review the call for the recurring transaction in the application code (if we have access to the Base44 code — the question is whether the generator allows export). Fourth — fix after identifying the specific cause, testing on a Tpay test account (sandbox) and then on a real account with a small amount.

Question for you: does Base44 allow editing/exporting the code, or can the fix only be implemented through their interface? Do you have access to the panel? Expand

Budget: 800 PLN Deadline: 1 day

Good day. I am ready to complete this project as I have extensive experience in application development.

Budget: 1200 PLN Deadline: 30 days

Hello! I have reviewed your task and believe that I can successfully complete it. I would be happy to collaborate, please write to me personally for further details.

Budget: 1500 PLN Deadline: 7 days

Freelancehunt

Jobs for freelancers

Integration of Tpay with a custom application
Hybrid mobile applications, Android programming — incorrect categories provided?
2 of 6
accepting offers
Next step: approval of terms

I will commission the integration of the Tpay payment gateway with my custom application. The goal is to correctly implement automatic subscription renewal through recurring BLIK payments, which are already set up, but there is a problem with renewal. The application is being created by me using AI on the Base44 website. The application works (Play Store Strefa Przemienieni.pl), I am not a programmer and I have a problem with integration. The whole system seems to work and charges the user money on the first transaction, saving it in the bank as a recurring payment, but there is a problem with BLIK aliases and when the subscription ends, it does not want to charge the fee again. The problem lies in the appropriate webhook lines App-> Tpay and Tpay -> App.

Offers 8
Discussion 0

1988
10 0
Example of work:
How Gemini API devoured 180 dollars in a month: the real economy of AI
30 days 2500 PLN
Arseny Antonenko

I will inspect the logs and implement correct renewal handling through the Tpay API (recurring method using saved cli_auth), without involving the user in re-entering the BLIK code. Simple financial issues — in a private message.

The problem with recurring BLIK usually arises because during the next charge attempt (when the subscription expires), the application sends a request as a standard, one-time BLIK instead of the method api/v1/transaction/execute-saved-alias, or the server does not properly process the asynchronous notification (Notification URL) from Tpay confirming the registration of the user's alias. Do you currently have the ability to view what exactly Tpay returns in the logs at the moment when the application tries to automatically renew the subscription?

Similar completed order: Fix 5 issues related to Facebook API in the OpenCart module
May 26, 20:40
685
5 0

7 days 2000 PLN
Maksym O.

Hi, I worked on integrating Stripe with a mobile application for a fitness studio, where I configured automatic monthly subscription charging with a 95% transaction success rate for 150+ active users.

I wonder if the webhook problem occurs only for BLIK, or if other payment methods also have issues with subscription renewals?

I suggest contacting me, I would be happy to advise you for free with technical issues. Expand

Budget: 18000 PLN Deadline: 6 days

Hello. The task is clear: not just an "AI bot," but a proper system that regularly retrieves tenders from Prozorro, filters out the unnecessary, explains why a tender is suitable/not suitable, and sends this information to Telegram.

Here’s what I would do:
1. A separate backend process for monitoring Prozorro and storing the state, so as not to miss new tenders and avoid sending duplicates.
2. Filtering rules + AI analysis on top of already cleaned data, so the model doesn’t fantasize but works based on clear criteria.
3. A Telegram bot with short cards: essence of the tender, deadline, amount, why it’s relevant, link, quick actions.
4. Logs/errors/retries, because such systems should operate smoothly without manual supervision.

I had a similar project in logic: an n8n/PostgreSQL/OpenAI/Telegram system that analyzed data every day and sent people specific tasks, not just "AI text."
Regarding timelines: the target is 6 days. For the budget: 18,000 — after a brief clarification of the technical specifications, I will confirm the exact amount, but this is the general range.

If this is okay, I will start with a short architecture diagram and a list of clarifications to immediately fix the MVP without unnecessary development. Expand

Budget: 1000 PLN Deadline: 5 days

Good morning. I have extensive experience in payment integrations, APIs, and webhooks. I can check the current implementation of Tpay/Base44 and fix the issue with subscription renewals and BLIK aliases. Please provide access to the code and the test panel, then I will assess the exact scope and timeline.

Budget: 2000 PLN Deadline: 5 days

Hello. My name is Roman, CVO of Echocode. Digital
We have an experienced team with 8 years of expertise in creating turnkey websites, mobile applications, and complex web systems.
Over 8 years of practice, we have developed a deep technical stack.
You won't need to separately look for a designer, backend developer, and frontend developer. Our team works in a single unit, which eliminates misunderstandings between design and code, significantly speeds up development, and guarantees a quality result from one source.
Message us privately! We will discuss the details of your project, calculate exact timelines and budget.
Freelancehunt