Optimización de sección Balance

Problema actual: existe cierta incertidumbre sobre el tiempo de liberación de los fondos, ya que varía según el método de pago, banco o tarjeta. Además, el proceso de extracción es manual o requiere la intervención del equipo de soporte, lo que genera fricción y demora en la disponibilidad del capital. Propuesta de mejora: Calendario de Liquidación: Sería genial tener una vista de calendario o cronograma, dentro de la sección Balance. Esto nos daría una previsibilidad financiera total. Visualización: Poder ver qué días de la semana/mes se liberarán montos específicos (ej: "Lunes 23: Se liberan ARS $50.000"). Trazabilidad: Al hacer clic en una fecha, ver el desglose de los cobros que componen ese monto, clientes, su método de pago y el motivo del plazo (ej: 72hs hábiles por tarjeta de crédito). Automatización de Retiros: Añadir una opción para configurar "Retiros Automáticos". La idea sería poder elegir que, una vez que los fondos pasen al estado "Disponible", se transfieran automáticamente a la cuenta bancaria vinculada sin necesidad de realizar el pedido manual o contactar a soporte.

Lucas Nasich 6 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 7 days ago

💡 Feature request

Validacion de email

Buenos días, ayer tuve un problema con la validación de los mails, un nuevo suscriptor puso .comi en vez de .com y pudo avanzar. Se frenó toda la automatización y los correos obviamente no llegaron. Lo corregí de forma manual. Adjunto captura. Saludos a todo el equipo !

Leandro Bustingorry 19 days 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 20 days ago

💡 Feature request

Problema con logs de pagos rechazados

Hola, equipo. Quisiera consultar si es posible obtener motivos de rechazo más específicos en el log de transacciones. Actualmente, la información es demasiado genérica y nos impide dar soporte real al cliente. Por ejemplo, tenemos un caso de una suscripción anual donde el cliente ya intentó con tarjeta Cordobesa y Naranja, ambos intentos fallidos sin una causa clara. Necesitamos mayor visibilidad para saber si el problema es de nuestra configuración, del procesador o un bloqueo del emisor, y así evitar perder la venta. ¿Existe algún código de error detallado que podamos consultar?

Lucas Nasich 21 days ago

1

💡 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 21 days ago

1

💡 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 24 days 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 27 days ago

💡 Feature request

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 27 days 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 28 days 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 1 month ago

3

💡 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 1 month 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 1 month ago

💡 Feature request

Deshabilitar datos de usuario en Checkout SDK

Me topé con una discrepancia entre el sandbox y el modo productivo usando el Checkout SDK. En el modo sandbox, estoy pasando los datos de usuario (email y nombre) como prop del componente y estoy ocultando que esos datos (customerInformation) se pidan al usuario al momento de completar el pago. Esto funciona correctamente y el pago se procesa perfecto. En el modo productivo, este setup no funciona. El submit del formulario directamente no funciona, claramente no valida este setup. Al cambiar esta config a customerInformation: true, y mostrar los fields para que el usuario ingrese los datos de email y nombre, ahi el formulario valida y el submit funciona. El problema de esto (al menos que me este faltando información, agradecido si me la facilitan) es la identificación del usuario en el webhook para poder asignar ese estado de la suscripción en mi DB. Si el usuario es capaz de modificar su email al momento de realizar el pago, me quedaría una subscripción huérfana y tendría que identificar manualmente a que email pertenece ese usuario en mi DB.

Mauro Barrionuevo About 1 month 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 About 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 About 2 months ago

💡 Feature request

Problem with renewal links

Good morning, when I generate a link to collect the subscription fee (marked in green in the screenshot where I got it from), as soon as I access it, it tells me that the link has expired. Here is an example of a subscription where this is happening. (This has happened to me with several.) sub_53859cc3775544429361b61b16dbfa68

Leandro Bustingorry About 2 months ago

2

💡 Feature request

Discrepancia codigo de desuento

Buenos dias, cuando creo un codigo de descuento por un valor fijo, me descuenta mas al aplicarlo, adjunto id del codigo y capturas. Saludos. cpn_f0e318cb4cdf442c932e8ddaee6083b6

Leandro Bustingorry About 2 months ago

💡 Feature request

Buenas tardes, ¿hay posibilidad de que el enlace para el cambio de tarjeta, al copiarlo y enviarlo al alumno, pueda ser más corto? Te muestro a continuación un ejemplo de cómo se visualiza actualmente:

Romina Paulli 2 months ago

💡 Feature request