What This Page Covers#
For most refund rails, Cobre already has everything it needs to send the money back — the payer's account data travels with the original payin, so the refund settles automatically with no action from them. PSE and Bancolombia are the exception: those rails don't hand Cobre the payer's destination account, so the payer has to provide it before Cobre can execute the payout.When that happens, Cobre sends the payer a secure link where they enter their account details, confirm them, and verify their identity. This page walks through exactly what the payer sees on that link, so you can set expectations with them and answer support questions when they come up.
When Your Payer Needs to Act#
A refund only requires payer input on r2p_pse and r2p_bancolombia. On every other supported rail (direct_debit/Nequi Tokenization, r2p_breb, r2p_nequi, breb_credit) the refund resolves and pays out automatically — the payer never sees a link.For PSE and Bancolombia, the refund is created in waiting_for_information status and Cobre generates:A capture link for the payer to open and complete.
An expiration timestamp for that link.
Once the payer submits and confirms their details, the refund moves to processing and follows the same lifecycle as every other rail from there (processing → completed / failed / rejected). See the Refund API guide for the full state diagram and webhook events.If the payer doesn't complete the link before it expires, the refund is rejected. You'll need to trigger a new refund for the payer to try again.
The Payer's Experience, Step by Step#
The capture link opens a standalone, mobile-friendly page — no Cobre account or login required. It's branded with your business name and Cobre's "generated securely by Cobre" footer, so payers recognize it as a legitimate part of completing their refund, not a separate unrelated request.The screenshots below are for reference only. The real UI may vary subtly (copy, styling, field order).
1. Choosing how to receive the refund#
The page opens with the refund context already filled in — your business name, the refund amount, and a reference to the original operation (for example, "[Business name] autorizó un reembolso de [amount] para la operación •••• 1234").The payer picks one of two destination types:| Field | Description |
|---|
| Nombre del Titular | Name on the destination account |
| Tipo de documento | ID type (dropdown) |
| Número de documento | ID number |
| Tipo de cuenta | Account type, e.g. Ahorros (dropdown) |
| Número de cuenta | Destination account number |
| Entidad financiera | Destination bank (dropdown, shown with the bank's logo) |
| Field | Description |
|---|
| Nombre del Titular | Name on the Bre-B key |
| Tipo de documento | ID type (dropdown) |
| Número de documento | ID number |
| Llave / identificador | The payer's Bre-B key |
The Confirmar y solicitar el reembolso button stays disabled until every required field is filled and the consent checkbox (next section) is checked.2. Authorization and consent#
Below the form, a data-processing disclosure explains that the information the payer submits will be used to execute and credit the refund, handle failures or claims, and keep a traceability record — processed by Cobre and its providers on your business's behalf.The payer must check "He leído y acepto la Autorización y consentimiento". The linked text opens an overlay with the full consent language, covering:What the data will be used for and who processes it.
The payer's rights (access, correction, deletion, revoking authorization, requesting proof of use, filing complaints with the SIC).
Acceptance of the data processing policy.
The payer taps Aceptar to close the overlay; the checkbox is then available to mark on the main form.3. Confirming the details#
Submitting the form moves to a "Confirma tus datos" review screen, showing:Resumen — the amount to be received.
Detalle — the original request number, the refund reference, the destination entity, the masked account number, and the account holder's name.
A final checkbox confirms the payer understands the deposit will appear on their bank statement under Cobre's legal entity name, and that the data shown is correct and will be used exactly as entered. The payer can go Volver (back to edit) or continue with Confirmar y continuar.4. Verifying identity#
Confirming triggers a one-time-code check: a modal shows "Verifica tu identidad", with a 6-digit code sent to the payer's masked email (e.g. a***@correo.com). The payer enters the code and taps Verificar código.A countdown (starting at 60 seconds) gates the Reenviar código button — it only becomes active once the countdown reaches zero, to prevent request spamming.5. Processing#
Once the code is verified, the refund request is submitted and the page shows "Estamos procesando tu reembolso", with the same Resumen/Detalle summary as the confirmation step. This is the moment the refund transitions from waiting_for_information to processing on your side — any webhook subscriber receives refund.status.processing at this point.The page offers a "Volver a [tu comercio]" button so the payer can return to your site without waiting for the final result (Only if you use the redirect_url optional field in the API).6. Final outcome#
When the underlying payout settles, the payer's status page updates (if they're still there) or they can be redirected back once it's final:Completed — "Tu reembolso fue exitoso": confirms the money was sent to their bank account.
Rejected / Failed — "No pudimos procesar tu reembolso": tells the payer the refund couldn't be completed and to request a new one directly with your business.
Both terminal screens keep the same Resumen/Detalle summary and a return-to-merchant button.
Status Reference#
| What the payer sees | Underlying refund.status.state |
|---|
| Form screen (destination + consent) | waiting_for_information |
| "Estamos procesando tu reembolso" | processing |
| "Tu reembolso fue exitoso" | completed |
| "No pudimos procesar tu reembolso" | failed or rejected |
Full field-level detail (status.code, status.description, webhook payloads) is documented in the Refund API guide's Refund Lifecycle section.
What to Tell Your Payer#
"Is this link safe?" Yes — it's generated and hosted by Cobre specifically for this refund, shows your business name, and never asks for banking credentials or passwords, only the destination account or Bre-B key to send the money to."The link says it's expired." The payer needs a new refund request from you — trigger a new refund and a fresh link will be generated."I confirmed my details but nothing happened." Check the refund's status on your side. If it's still processing, the payout is in flight; if rejected or failed, the payer's details may need to be resubmitted through a new refund request."I didn't get the verification code." Codes are sent to the masked email shown on screen. If it doesn't arrive, the payer can wait for the resend countdown to finish and request a new one. If the problem persists, please contact support.