Redsys virtual POS
The one you sign up for with your bank, with payment on the Redsys page or embedded in your site, 3D Secure authentication and a server notification so the order is confirmed even if the customer never comes back.
At a Spanish online shop, customers expect at least cards, Bizum and PayPal, and for pricier items more and more of them want to spread the cost. Adding the buttons is the easy part. The hard part is everything else: the order must update even if the customer closes the browser before returning to the shop, a Bizum refund should be triggered from the order without logging into the bank portal, the daily settlement from the virtual POS has to match the day's orders, and each method's fees need to land in the right account. When one piece fails, you end up with a customer who has paid and gets a “pending order” email, or an accounts team hunting on a Friday afternoon for the source of €2,318.45 on the bank statement.
We do not just compare fees. We look at which methods your customers need, what your bank offers and whether the gateway produces a report the accounts team can actually use.
The one you sign up for with your bank, with payment on the Redsys page or embedded in your site, 3D Secure authentication and a server notification so the order is confirmed even if the customer never comes back.
Enabled through Redsys and your bank, and increasingly popular for small and mid-sized orders. Full or partial refunds straight from the order.
Stripe for cards, Apple Pay and Google Pay when you want a gateway independent of your bank; PayPal because some of your customers will not buy without it.
seQura or Aplazame for high baskets in furniture, appliances, bikes or training courses. The cost is weighed against the extra sales, not against the card fee.
SEPA direct debit for subscriptions, bank transfer on terms for account customers, and an automatic reminder a few days before the due date.
Some sectors and customers still ask for it. We link it with the carrier and the ERP, and flag the cost and the risk of refused parcels.
Each gateway's settlements are broken down by order, fees are split out and the accounts team stops ticking off statements by hand.
The technical integration is rarely the slowest part. Bank paperwork for the virtual POS and the gateway's review of your site take longer, so that is where we start.
Fees per method, refund costs, settlement times and available features, modelled on your real volumes.
A legal notice under the LSSI, terms of sale including the right of withdrawal, returns and privacy policies, and VAT-inclusive prices for consumers.
Checkout payment, server notifications, regular polling of pending payments and handling of the strong customer authentication required by PSD2.
One genuine payment and one refund with every method before the shop goes live. It is a planned step, not a last-minute check.
Test the refund before the payment. Every shop tests taking money; hardly any check what happens when €12.30 must be returned from a three-item order paid by Bizum, or when a customer disputes the charge with their bank six weeks later. Those are the cases that end in angry messages and books that refuse to balance, so we settle and document them before launch.
It depends. Redsys fees are often negotiable with your bank and it is the natural route to Bizum, but sign-up and changes go through the bank. Stripe switches on quickly, has good documentation and a handy dashboard, with published fees. Many shops use both: Redsys for cards and Bizum, with Stripe or PayPal as an alternative.
In the usual seQura or Aplazame model, the finance provider pays you for the order and collects from the customer, but the exact terms are in the contract and deserve a careful read. The sum to do is what the method costs against how much it lifts the average basket and conversion.
It depends on the gateway. Redsys usually settles through your bank, with fees shown according to your agreement with it; Stripe and PayPal settle net and issue their own fee invoice. The integration separates gross, fee and net for every order, and your accountant picks the ledger account.
That depends on the number of methods, the platform and whether reconciliation must feed the ERP. For a PrestaShop or WooCommerce shop using official modules, the work is mostly configuration and testing. We quote per project or charge by the hour at €75 per hour + VAT.
Tell us what you sell, on which platform and what share of your customers are businesses. We will suggest gateways and methods and wire them into your accounts.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.