Currently there are just 6 predefined roles with preset permisisons. For us it’s valuable to set permissions more granularly for some people who for example…don’t need to have access to link creation, balances, teams, but still be able to copy-send payment links to customers who reported that Rebill didn’t send them anything

egor-shchukin@tripleten.com 2 days ago

💡 Feature request

Hi, do you have any updates on this: https://product.rebill.com/es/p/marketplace-api? I'd like to use the Payouts API, if it's already available. I’m planning to develop an open-source plugin for Better Auth to simplify the logic needed to build marketplaces using Rebill. The basic idea would be as follows: 1 - When a user registers, a wallet associated with their account is automatically created. 2 - When using Instant Checkout, I send information such as wallet_id and user_id in the metadata. 3 - When a customer makes a payment, that payment is automatically associated with the corresponding user’s wallet. 4 - Subsequently, the user can request a withdrawal of the funds available in their wallet to their own account.

Nicolas Lujan 11 days ago

2

💡 Feature request

Currently if we need to find a specific link in, we need to search by their title. Searching by link id or by full link would enable faster search on the dashboard

egor-shchukin@tripleten.com 18 days ago

1

💡 Feature request

Hello, As part of our development, we would need to be able to access invoices to show them on our platform. We only see the option to send them via email automatically, but we'd like to access them via the API or receive them via webhooks so we can show the to the consumers later on. Is there a way to achieve this? Thanks in advance!

Josefina Urquiza about 1 month ago

💡 Feature request

Plase Design an Invoice with more Love!

Josefina Urquiza about 1 month ago

💡 Feature request

This feature exists in Stripe and seriously helps us find undocumented payments from different emails in case customers claim that they paid, but we can’t find the payment

egor-shchukin@tripleten.com about 1 month ago

1

💡 Feature request

Hi! Currently we can only see generic reason of failure in the dashboard (Rejected by the card issuing bank. Ask the user to try later or use another method.). It would help us to also see errorStatusDetail (do_not_honor) in the dashboard to give more detailed explanations to our customers

egor-shchukin@tripleten.com about 1 month ago

💡 Feature request

Hi, team! It would be great if you could add direct integration with Meta’s Conversions API (CAPI) and the Pixel on the checkout screens. These days, it’s very difficult to track campaigns effectively using just the browser. Plus, with Meta’s new algorithm (Meta Andromeda), the system absolutely needs clean data from the server to understand who’s actually making purchases. Without this, the algorithm is working blindly, and it’s nearly impossible to scale sales profitably. Being able to send purchase events (especially via CAPI from server to server) isn’t a luxury—it’s a key necessity for any business that uses paid traffic today. The benefit? We all win: If we merchants can properly feed Meta’s algorithm, we’ll sell a lot more. And as we sell more, Rebill will naturally process a much higher volume of payments. I hope they can add this to the roadmap soon! It would be a huge win.

victor 2 months ago

💡 Feature request

We request visibility and follow-up on each case so that we can know its status at all times: whether it is still being processed, or whether it was resolved in favor of the buyer or in favor of the company.

rominapaulli@msklatam.com 3 months ago

💡 Feature request

We would love to have an ability to set up uneven charges with a specific customizable date of next payment. Example: 1st payment: 18000 MXN 2nd payment: 3500 MXN, +26 days 3rd payment: 3500 MXN, next month 4th payment: 3500 MXN, next month Currently we have to use product + plan mix to be able to provide such option

egor-shchukin@tripleten.com 3 months ago

💡 Feature request

Good afternoon, I'm not receiving the subscription events for Make. Here's the link to the webhook. Best regards. https://hook.us2.make.com/twuxiqib5veksvuixm5s1bythuhtpudp

Leandro Bustingorry 3 months ago

💡 Feature request

Currently if we check chargebacks in the new dashboard, they are all linked to the original payment date and we don’t even know when they were initiated. As a result, we don’t know which ones we can counterdispute and which ones we can’t

egor-shchukin@tripleten.com 3 months ago

💡 Feature request

Incrementar la cantidad de reintentos de cobro, sumando 3 adicionales, para alcanzar un total de 7 intentos. Permitir la activación y el cobro manual mientras la operación se encuentra en estado “reintentando”, sin necesidad de esperar 48 horas. Esto resulta clave especialmente el último día del mes, ya que el alumno puede informar que ya percibió sus haberes y está en condiciones de abonar. De esta forma, se evita considerarlo como no recuperado dentro del mes vigente y mejora el porcentaje de recupero. Reducir la longitud del link de cambio de tarjeta, para facilitar su uso y envío. Simplificar los campos del link de pago, eliminando la obligatoriedad de completar domicilio y código postal. Incorporar la visualización del tipo de tarjeta en la plataforma (crédito, débito o prepaga).

rominapaulli@msklatam.com 3 months ago

💡 Feature request

Hi, how are you? I think you have a great solution, but it’s very difficult for an LLM to process your developer page. I don't mean to name the competition, but Mercado Libre has three things you could add: Documentation in .md format An MCP server for the documentation An AI chatbot for inquiries (once the MCP server is up and running, this would be the natural next step) I hope you find my recommendation helpful. Best regards!!

Miguel Ovejero 4 months ago

1

💡 Feature request

Hola equipo! Necesitamos ayuda para diagnosticar la autenticación de webhooks en producción, porque las requests entrantes no están alineando con el esquema de seguridad documentado. Contexto: Endpoint: https://mercantis.io/api/rebill/webhook Content-Type procesado: application/json Implementamos validación HMAC SHA-256 según docs (x-rebill-signature + secreto compartido) También probamos allowlist de IPs (34.225.22.63, 3.221.139.192) Comportamiento observado: Las requests entrantes no incluyen x-rebill-signature (ni headers equivalentes de firma) IP de origen observada en logs: 52.158.209.200 (fuera de la allowlist documentada) Resultado: 401 en el 100% de los intentos (no es intermitente) Importante: Esta integración venía funcionando correctamente. No rotamos API keys ni cambiamos la URL del webhook. ¿Nos pueden confirmar el contrato de autenticación vigente para webhooks en producción? Si lo necesitan, podemos compartir request IDs y timestamps exactos de entregas fallidas.

Lucas Nasich 4 months ago

2

📥 Feedback

Hola equipo! Necesitamos ayuda para diagnosticar la autenticación de webhooks en producción, porque las requests entrantes no están alineando con el esquema de seguridad documentado. Contexto: Endpoint: https://mercantis.io/api/rebill/webhook Content-Type procesado: application/json Implementamos validación HMAC SHA-256 según docs (x-rebill-signature + secreto compartido) También probamos allowlist de IPs (34.225.22.63, 3.221.139.192) Comportamiento observado: Las requests entrantes no incluyen x-rebill-signature (ni headers equivalentes de firma) IP de origen observada en logs: 52.158.209.200 (fuera de la allowlist documentada) Resultado: 401 en el 100% de los intentos (no es intermitente) Importante: Esta integración venía funcionando correctamente. No rotamos API keys ni cambiamos la URL del webhook. ¿Nos pueden confirmar el contrato de autenticación vigente para webhooks en producción? Si lo necesitan, podemos compartir request IDs y timestamps exactos de entregas fallidas.

Lucas Nasich 4 months ago

1

📥 Feedback

Buenos dias, estaría bueno que se implemente un segundo método de verificación cuando se intenta abrir la cuenta en un dispositivo nuevo. Actualmente solo con la clave ya se puede ingresar en cualquier computadora. Un app de autenticación, SMS o mail, si es mas de uno mejor. Saludos.

Leandro Bustingorry 4 months ago

💡 Feature request

Si un cliente se da de baja, no se le cobró, u ocurre otro escenario, como comercio quiero estar al tanto y no depender de los webhooks. Si tan solo pudiesen enviar un mail sería ideal para estar al tanto

Ariel Lipschutz 4 months ago

1

💡 Feature request

A la hora de crear cuenta, el sistema pide ingresar un mail corporativo. Estaria bueno que el producto esté disponible para personas físicas.

Tadeo Maddonni 4 months ago

1

💡 Feature request