Link creation, transaction pages revert back to vanilla state & 1st page
Every time there’s a change on the page - for example, we extend it to check earlier links, when we open it & go back - page reverts back to original state. Example:
egor-shchukin 6 days ago
💡 Feature request
Link creation, transaction pages revert back to vanilla state & 1st page
Every time there’s a change on the page - for example, we extend it to check earlier links, when we open it & go back - page reverts back to original state. Example:
egor-shchukin 6 days ago
💡 Feature request
Docs
Agregar un boton de Copy to LLM que copie una skill tipo sentry que te copia Deberia estar en la home de cada feature principal.
Matias Solina 7 days ago
💡 Feature request
Docs
Agregar un boton de Copy to LLM que copie una skill tipo sentry que te copia Deberia estar en la home de cada feature principal.
Matias Solina 7 days ago
💡 Feature request
FORCE PAYMENT FOR PAUSED SUBSCRIPTION
Forcing payment for a subscription can only be done when it is active. Is there any possibility of doing this when it is paused? I have clients who ask me to try to charge them, and I have to activate the subscription to do so. If this is not done, the client remains active with access to the course without payment. On the other hand, it would be great if you could add the option to force it while paused. If it is not charged, it remains paused, and if it is charged, it goes directly to active status. Thank you very much.
Leandro Bustingorry 10 days ago
💡 Feature request
FORCE PAYMENT FOR PAUSED SUBSCRIPTION
Forcing payment for a subscription can only be done when it is active. Is there any possibility of doing this when it is paused? I have clients who ask me to try to charge them, and I have to activate the subscription to do so. If this is not done, the client remains active with access to the course without payment. On the other hand, it would be great if you could add the option to force it while paused. If it is not charged, it remains paused, and if it is charged, it goes directly to active status. Thank you very much.
Leandro Bustingorry 10 days ago
💡 Feature request
Section optimization Balance
Current problem: There is some uncertainty about the time it takes for funds to be released, as this varies depending on the payment method, bank, or card. In addition, the withdrawal process is manual or requires the intervention of the support team, which creates friction and delays in the availability of capital. Proposed improvement: Settlement Calendar: It would be great to have a calendar or schedule view within the Balance section. This would give us total financial predictability. Visualization: Being able to see which days of the week/month specific amounts will be released (e.g., "Monday 23: ARS $50,000 released"). Traceability: When clicking on a date, see the breakdown of the charges that make up that amount, customers, their payment method, and the reason for the term (e.g., 72 business hours by credit card). Withdrawal Automation: Add an option to set up "Automatic Withdrawals." The idea would be to be able to choose that, once the funds are in "Available" status, they are automatically transferred to the linked bank account without having to make a manual request or contact support.
Lucas Nasich 20 days ago
💡 Feature request
Section optimization Balance
Current problem: There is some uncertainty about the time it takes for funds to be released, as this varies depending on the payment method, bank, or card. In addition, the withdrawal process is manual or requires the intervention of the support team, which creates friction and delays in the availability of capital. Proposed improvement: Settlement Calendar: It would be great to have a calendar or schedule view within the Balance section. This would give us total financial predictability. Visualization: Being able to see which days of the week/month specific amounts will be released (e.g., "Monday 23: ARS $50,000 released"). Traceability: When clicking on a date, see the breakdown of the charges that make up that amount, customers, their payment method, and the reason for the term (e.g., 72 business hours by credit card). Withdrawal Automation: Add an option to set up "Automatic Withdrawals." The idea would be to be able to choose that, once the funds are in "Available" status, they are automatically transferred to the linked bank account without having to make a manual request or contact support.
Lucas Nasich 20 days ago
💡 Feature request
Cambio de Tarjeta
Es posible obtener alguna notificacion cuando el cliente utiliza el endpoint https://docs.rebill.com/api/reference/subscriptions#create-card-update-link y actualiza su tarjeta correctamente?
Sebastian Concha 21 days ago
💡 Feature request
Cambio de Tarjeta
Es posible obtener alguna notificacion cuando el cliente utiliza el endpoint https://docs.rebill.com/api/reference/subscriptions#create-card-update-link y actualiza su tarjeta correctamente?
Sebastian Concha 21 days ago
💡 Feature request
Email validation
Good morning, yesterday I had a problem with email validation. A new subscriber entered .comi instead of .com and was able to proceed. The entire automation process was halted, and the emails obviously did not arrive. I corrected it manually. Attached is a screenshot. Greetings to the whole team!
Leandro Bustingorry About 1 month ago
💡 Feature request
Email validation
Good morning, yesterday I had a problem with email validation. A new subscriber entered .comi instead of .com and was able to proceed. The entire automation process was halted, and the emails obviously did not arrive. I corrected it manually. Attached is a screenshot. Greetings to the whole team!
Leandro Bustingorry About 1 month ago
💡 Feature request
Batch deactivation of payment links
We have encountered an issue of usage of incorrect links and we would love to have batch unpublish feature where we could choose link with a checkbox and make certain actions with it (deactivate/unpublish/delete/publish & etc.)
egor-shchukin About 1 month ago
💡 Feature request
Batch deactivation of payment links
We have encountered an issue of usage of incorrect links and we would love to have batch unpublish feature where we could choose link with a checkbox and make certain actions with it (deactivate/unpublish/delete/publish & etc.)
egor-shchukin About 1 month ago
💡 Feature request
Problem with rejected payment logs
Hello, team. I would like to ask if it is possible to obtain more specific reasons for rejection in the transaction log. Currently, the information is too generic and prevents us from providing real support to the customer. For example, we have a case of an annual subscription where the customer already tried with a Cordobesa and Naranja card, both attempts failed without a clear cause. We need greater visibility to know if the problem is with our configuration, the processor, or a block from the issuer, and thus avoid losing the sale. Is there a detailed error code we can consult?
Lucas Nasich About 1 month ago
💡 Feature request
Problem with rejected payment logs
Hello, team. I would like to ask if it is possible to obtain more specific reasons for rejection in the transaction log. Currently, the information is too generic and prevents us from providing real support to the customer. For example, we have a case of an annual subscription where the customer already tried with a Cordobesa and Naranja card, both attempts failed without a clear cause. We need greater visibility to know if the problem is with our configuration, the processor, or a block from the issuer, and thus avoid losing the sale. Is there a detailed error code we can consult?
Lucas Nasich About 1 month ago
💡 Feature request
Add the ability to immediately provide another PSE application if customer for some reason failed existing one
Currently we know about the limitation of PSE in V3 - if first attempt fails for some reason, customer has to wait for 20 mins. We understand that this is not caused by you, however we 100% need a workaround for this situation. Currently we use V2 whenever there’s a failure in V3, however with deprecating V2 it becomes a critical blocker for us - we can’t risk significant portion of the sales because of this
egor-shchukin About 1 month ago
💡 Feature request
Add the ability to immediately provide another PSE application if customer for some reason failed existing one
Currently we know about the limitation of PSE in V3 - if first attempt fails for some reason, customer has to wait for 20 mins. We understand that this is not caused by you, however we 100% need a workaround for this situation. Currently we use V2 whenever there’s a failure in V3, however with deprecating V2 it becomes a critical blocker for us - we can’t risk significant portion of the sales because of this
egor-shchukin About 1 month ago
💡 Feature request
Pre-fill document type and number via API (prefilledFields)
Problem Currently, prefilledFields.customer in the Payment Links API only supports: email, fullName, phoneNumber, countryCode, and language. There's no way to pre-fill document type (typeIdNumber) and document number (idNumber) via the API payload. This forces merchants to use Custom JS workarounds with URL query parameters, which: Requires extra frontend development Is fragile and undocumented Doesn't work reliably across all scenarios Use Case When a customer completes checkout on our e-commerce platform, we already collect their document. We want to pass this data to Rebill to avoid asking the customer to re-enter it. Proposed Solution Add these fields to prefilledFields.customer Benefits Reduces friction at checkout and improves conversion rates Consistent with how phone prefill works (recently added) No need for Custom JS workarounds
Vic R About 1 month ago
💡 Feature request
Pre-fill document type and number via API (prefilledFields)
Problem Currently, prefilledFields.customer in the Payment Links API only supports: email, fullName, phoneNumber, countryCode, and language. There's no way to pre-fill document type (typeIdNumber) and document number (idNumber) via the API payload. This forces merchants to use Custom JS workarounds with URL query parameters, which: Requires extra frontend development Is fragile and undocumented Doesn't work reliably across all scenarios Use Case When a customer completes checkout on our e-commerce platform, we already collect their document. We want to pass this data to Rebill to avoid asking the customer to re-enter it. Proposed Solution Add these fields to prefilledFields.customer Benefits Reduces friction at checkout and improves conversion rates Consistent with how phone prefill works (recently added) No need for Custom JS workarounds
Vic R About 1 month ago
💡 Feature request
Ability to create promocode inside existing coupons instead of creating new coupons every time
Promocodes are parts of promocampaigns, however, in rebill promocodes are almost the same thing as coupons because you can’t add promocodes to the existing coupons (promocampaigns). This slows down promocode creation and increases chance to make a mistake during creation
egor-shchukin About 1 month ago
💡 Feature request
Ability to create promocode inside existing coupons instead of creating new coupons every time
Promocodes are parts of promocampaigns, however, in rebill promocodes are almost the same thing as coupons because you can’t add promocodes to the existing coupons (promocampaigns). This slows down promocode creation and increases chance to make a mistake during creation
egor-shchukin About 1 month ago
💡 Feature request
Completed
Ability to edit customized end date of subscription
Currently if incorrect information is inputted in the link, you can’t doublecheck it and can’t change it, which makes it difficult to investigate issues with manual links
egor-shchukin About 1 month ago
💡 Feature request
Completed
Ability to edit customized end date of subscription
Currently if incorrect information is inputted in the link, you can’t doublecheck it and can’t change it, which makes it difficult to investigate issues with manual links
egor-shchukin About 1 month ago
💡 Feature request
Ability to duplicate preexisting links to save time on creation
On our side we regularly create very similar links changing only a handful of parameters (price) while leaving everything as is without changes. Ability to duplicate and edit existing links can cut time on link creation by half or even more depending on the situation
egor-shchukin About 1 month ago
💡 Feature request
Ability to duplicate preexisting links to save time on creation
On our side we regularly create very similar links changing only a handful of parameters (price) while leaving everything as is without changes. Ability to duplicate and edit existing links can cut time on link creation by half or even more depending on the situation
egor-shchukin About 1 month ago
💡 Feature request
Offer payment in installments for an annual subscription
It would be great to offer our customers the option of paying for their annual plan in installments. We would secure their loyalty for longer, and they would get the promotional annual price without having to pay all the money up front. It's a great incentive to increase conversions for annual plans.
Lucas Nasich About 2 months ago
💡 Feature request
Offer payment in installments for an annual subscription
It would be great to offer our customers the option of paying for their annual plan in installments. We would secure their loyalty for longer, and they would get the promotional annual price without having to pay all the money up front. It's a great incentive to increase conversions for annual plans.
Lucas Nasich About 2 months ago
💡 Feature request
Change pending status for waiting for refund cases to "pending refund"
Right now we sometimes misunderstand what is the actual state of transaction and was there a payment in the first place because in case of refund, transaction then first transfers to pending state. As there’s also a pending state before the payment, this becomes nontransparent. We would like to have separate naming for such state
egor-shchukin About 2 months ago
💡 Feature request
Change pending status for waiting for refund cases to "pending refund"
Right now we sometimes misunderstand what is the actual state of transaction and was there a payment in the first place because in case of refund, transaction then first transfers to pending state. As there’s also a pending state before the payment, this becomes nontransparent. We would like to have separate naming for such state
egor-shchukin About 2 months ago
💡 Feature request
Please review as a priority (subscriptions that are not charged).
Good afternoon, today while reviewing, I found four subscriptions that were not charged a month or more ago and remained active. No further attempts were made either. I am attaching them here for you to review. I will continue to look to see if I can find any more. sub_7b70899711ac45c893a0edd4a9dd469e sub_d8b90f8275d6437287a794ab6387f3eb sub_cd265f08775a4e2195eb11a9f04301df sub_2f88301a290341059680038e6381778d
Leandro Bustingorry About 2 months ago
💡 Feature request
Please review as a priority (subscriptions that are not charged).
Good afternoon, today while reviewing, I found four subscriptions that were not charged a month or more ago and remained active. No further attempts were made either. I am attaching them here for you to review. I will continue to look to see if I can find any more. sub_7b70899711ac45c893a0edd4a9dd469e sub_d8b90f8275d6437287a794ab6387f3eb sub_cd265f08775a4e2195eb11a9f04301df sub_2f88301a290341059680038e6381778d
Leandro Bustingorry About 2 months ago
💡 Feature request
Disable user data in Checkout SDK
I encountered a discrepancy between the sandbox and production mode using the Checkout SDK. In sandbox mode, I am passing user data (email and name) as a component prop and hiding the fact that this data (customerInformation) is requested from the user when completing the payment. This works correctly and the payment is processed perfectly. In production mode, this setup does not work. The form submission does not work at all; it clearly does not validate this setup. When I change this configuration to customerInformation: true, and display the fields for the user to enter their email and name, the form validates and the submit works. The problem with this (unless I am missing some information, which I would appreciate if you could provide) is the identification of the user in the webhook in order to assign that subscription status in my DB. If the user is able to change their email address at the time of payment, I would be left with an orphaned subscription and would have to manually identify which email address that user belongs to in my DB.
Mauro Barrionuevo About 2 months ago
💡 Feature request
Disable user data in Checkout SDK
I encountered a discrepancy between the sandbox and production mode using the Checkout SDK. In sandbox mode, I am passing user data (email and name) as a component prop and hiding the fact that this data (customerInformation) is requested from the user when completing the payment. This works correctly and the payment is processed perfectly. In production mode, this setup does not work. The form submission does not work at all; it clearly does not validate this setup. When I change this configuration to customerInformation: true, and display the fields for the user to enter their email and name, the form validates and the submit works. The problem with this (unless I am missing some information, which I would appreciate if you could provide) is the identification of the user in the webhook in order to assign that subscription status in my DB. If the user is able to change their email address at the time of payment, I would be left with an orphaned subscription and would have to manually identify which email address that user belongs to in my DB.
Mauro Barrionuevo About 2 months ago
💡 Feature request
Renewal link from the API
Hello! It would be great to be able to obtain/create a renewal link from the API, just like the request card change link. Having to manually generate the link to send it is quite cumbersome. I'm referring to this: If it already exists in the API, it would be great to add it to the documentation because I couldn't find it. Best regards
Juan Pablo Accinelli About 2 months ago
💡 Feature request
Renewal link from the API
Hello! It would be great to be able to obtain/create a renewal link from the API, just like the request card change link. Having to manually generate the link to send it is quite cumbersome. I'm referring to this: If it already exists in the API, it would be great to add it to the documentation because I couldn't find it. Best regards
Juan Pablo Accinelli About 2 months ago
💡 Feature request
Access to Coupon Redeems
It would be great if I could access to payments that are associated to an specific coupon - now, I have to navigate through every payment and revise each to know if a discount was applied or not.
Nicolas Kenny 2 months ago
💡 Feature request
Access to Coupon Redeems
It would be great if I could access to payments that are associated to an specific coupon - now, I have to navigate through every payment and revise each to know if a discount was applied or not.
Nicolas Kenny 2 months ago
💡 Feature request
Agregar botón "Volver a la tienda" en el Checkout
Estaría bueno agregar un botón de retorno a la página de inicio dentro del flujo de checkout, tal como lo hace Stripe. El objetivo es permitir que el cliente regrese a la tienda fácilmente si decide seguir comprando o revisar algo, evitando que se sienta "atrapado" y mejorando la experiencia de usuario (UX) para reducir el abandono.
Lucas Nasich 2 months ago
💡 Feature request
Agregar botón "Volver a la tienda" en el Checkout
Estaría bueno agregar un botón de retorno a la página de inicio dentro del flujo de checkout, tal como lo hace Stripe. El objetivo es permitir que el cliente regrese a la tienda fácilmente si decide seguir comprando o revisar algo, evitando que se sienta "atrapado" y mejorando la experiencia de usuario (UX) para reducir el abandono.
Lucas Nasich 2 months ago
💡 Feature request