Present the size, duration, tax and total price before the guest commits.
Payments and venues integration
Turn payment approval into timed locker access.
A guest chooses storage, accepts the price and pays. Once the payment outcome is confirmed, a specific Vpod locker becomes available for the agreed period—while extensions, refunds, access failures and reconciliation follow defined rules.
- Authorise before access
- Handle changes clearly
- Reconcile money and usage
Create the locker entitlement when the payment state permits access.
Relate payment, extension, refund and locker events during reconciliation.
The verified Adyen platform
In-person payments, terminals, refunds and reconciliation are established capabilities.
Adyen currently provides in-person payment solutions using payment terminals and mobile options. Its official documentation covers payment responses, notifications, refunds, transaction totals and reconciliation.
A proposed Vpod connection would add a separate operational decision: when does a confirmed payment create, extend, suspend or end a locker entitlement? That design can support paid storage inside venues, high-throughput event lockers, guest luggage storage and commercial leisure lockers.
No native Adyen connector, universal terminal compatibility or existing customer deployment is asserted. Payment state, locker access and financial settlement remain distinct records that must be joined by an agreed reference.
Make the purchase tangible
The guest buys time and receives one usable locker.
The user should not need to understand payment infrastructure. They need the right price, a clear outcome, secure access and a fair route when plans change or something fails.
The visual paid-storage journey
From “Pay £8.00” to “Locker V-204 ready”.
This realistic example is illustrative and is not evidence of deployed Adyen–Vpod functionality.
- 01 · CHOOSE
Select size, time and price
The guest chooses a medium locker for four hours and sees the full £8.00 charge.
- 02 · PAY
Confirm the payment outcome
The agreed payment flow returns an authorised, refused, cancelled or uncertain result.
- 03 · ENTITLE
Allocate timed storage
An authorised purchase creates the agreed locker entitlement and expiry time.
- 04 · ACCESS
Give the guest secure access
The supported PIN, QR code, mobile journey or other confirmed method opens V-204.
- 05 · USE
Store, reopen or extend
The guest uses storage within the paid period and can follow agreed extension rules.
- 06 · RECONCILE
Match payment and locker records
Order, payment, entitlement, door use, extension and refund outcomes can be reconciled.
Exceptions and changed circumstances
If payment is refused or uncertain, allocation fails, the locker door faults, the guest exceeds time or a refund is due, protect the guest from duplicate charging and route the case to a named venue, finance or support owner.
Governance across venues
Keep pricing, references, refund authority and finance reports consistent while documenting each site’s currencies, taxes, terminals, locker zones, trading hours, accessibility, support and event-specific rules.
Names, prices, orders, dates and lockers are illustrative. Adyen account structure, terminals, payment methods, supported responses, refunds, settlement, data direction and locker integration scope must be confirmed during solution design.
Who owns each decision
A commercial service that Finance and Operations can both explain.
Commercial Directors
Own price, duration, demand, refund policy, revenue targets and guest proposition.
See how Commercial Directors can monetise venue storage without adding queues →Venue Operators
Own guest flow, locker zones, opening hours, peak demand and on-site exceptions.
Plan faster ingress and self-service storage from the Operations perspective →Finance
Define tax, tender, refunds, settlement, reconciliation, chargebacks and reporting.
Compare the financial effect of CapEx and OpEx locker models →IT
Confirm architecture, references, terminals, security, monitoring and recovery.
Place payments inside the wider locker integration architecture →Fix the commercial storage bottlenecks
Reduce queues without losing revenue or guest trust.
Compare the paid-storage model
Staffed cloakroom payments versus connected self-service lockers.
See paid self-service in a live venue context
Co-op Live: remove the cloakroom queue.
The Co-op Live best-practice video shows why a high-volume venue benefits when guests control their own storage journey.
Watch Co-op Live Best Practice – Self-Service Lockers
Hospitality revenue and guest convenience
Ibis Geneva: paid luggage storage in practice.
Use the Ibis Geneva case study as relevant operational context for paid guest storage. It is not evidence of an Adyen integration.
Watch the Ibis Geneva case study →
Decisions before implementation
Confirm the commercial and technical contract end to end.
Price and booking
Set locker sizes, durations, currencies, taxes, discounts and booking expiry.
Payment state
Define which confirmed outcome permits allocation and how uncertain results are checked.
Entitlement
Choose locker, access method, reopening, extension and expiry rules.
Refund and exception
Set authority and treatment for cancellations, faults, duplicate charges and no-shows.
Reconciliation
Relate order, Adyen reference, locker, entitlement, extensions, refunds and settlement.
Sites and governance
Document terminals, accounts, reports, support, accessibility and local trading rules.
Integration availability, supported triggers, data direction and delivery scope must be confirmed during solution design. Exact behaviour depends on the agreed Adyen, Vpod and smart-locker configuration. This page does not claim a native connector, universal terminal or payment-method compatibility, certification, commercial relationship, customer deployment or functionality beyond the confirmed project scope.
Start with one real paid-storage journey
Show us how a guest pays, stores and leaves today.
Bring the price model, venue flow, Adyen setup, refund policy, reconciliation needs, locker rules, site differences and common exceptions.
Book an integration workshop







