Usage
Daily use
Section titled “Daily use”- The customer chooses Redsys (or Bizum) at checkout. The store posts a signed form to Redsys and the customer pays on the Redsys page (3-D Secure included).
- Redsys calls your store with the signed result. The order becomes paid only after the signature, the amount and the currency have been verified. Pages the customer lands on (OK / KO) are only courtesy pages.
- Open the order and the Redsys payment tab to see the status, the Redsys order number (12 characters), the answer code, the authorisation code and the refunds.
- To refund, enter an amount (empty = everything that is left) and a reason on that tab. Redsys checks that all refunds together never exceed the payment.
- Every payment attempt of the order is listed. If a customer paid twice (for example a slow Bizum confirmation and then a card), the second attempt is marked “Duplicate payment” and has its own refund form.
- Multi-Vendor (marketplace owner takes the payments): a cart with products of several vendors is paid as one Redsys payment. Each vendor order shows that payment and can refund only its own share of it; the “refund when the order status becomes” setting refunds that share too.
- If an order was edited while its payment was still pending and the paid amount no longer matches the order total, the payment is booked but the order is not marked paid; the tab says so. Refund the payment or adjust the order and set its status by hand.
- A payment that never got an answer after 3 days is set to “Expired”. A late notification from Redsys can still settle it.
If the customer comes back before the result arrives
Section titled “If the customer comes back before the result arrives”The add-on waits a few seconds for the notification. If it is still missing, the customer sees the order page, the cart stays empty and nothing can be paid twice. When the notification arrives the order is updated. Check Orders or the add-on’s transaction list later.
Refund results
Section titled “Refund results”| Status | Meaning |
|---|---|
| done | Redsys answered 0900: the refund was executed. |
| failed | Redsys refused it (for example the amount exceeds the payment). Nothing was refunded. |
| creating | The request is being sent. |
| result unknown (unconfirmed) | No clear answer (timeout, issuer unavailable). The amount stays reserved and nothing is repeated. Look the operation up in the Redsys portal and press It was executed or It was not executed on the order tab. |
Jobs, log and connection
Section titled “Jobs, log and connection”- Jobs: counts per state, the list with the last error, Retry, Remove and Run the queue now.
- Log: filter and export what happened and when. Keys and signatures are masked.
- Connection: merchant code, terminals, keys, signature version, Test connection, notification URL.
Bizum needs a terminal on which your bank activated it. In test mode use the Bizum test user published by Redsys (see the “Tarjetas y entornos de prueba” page); test amounts must stay low (Redsys states 10 EUR).
Screenshots: marketing/media/screenshots/ (connection page, payment method settings, order tab).