Direct line to Albis
JSON-RPC integration with the Albis platform — credit check and application in real time, without email back-and-forth.
Leasing contracts directly in the Shopware checkout — with live API, Flow Builder integration and mail templates per sales channel.
A complete leasing flow inside Shopware: API integration, application path in checkout, mail integration, optional detail page display — from a single source, no external tools.
The plugin extends Shopware 6 with its own payment method "Albis Leasing". In checkout, the business customer fills in all leasing data themselves, the plugin sends it to the Albis API, the credit check runs in real time, and the customer gets an answer immediately. You as the merchant receive all data in parallel and can process the contract as usual.
JSON-RPC integration with the Albis platform — credit check and application in real time, without email back-and-forth.
Specifically for B2B leasing — company data, bank details, optionally director data above a defined order value.
Activation and configuration per sales channel — different channels can use different Albis accounts.
From version 2.5 (SW 6.7) the plugin config supports an additional set of Albis credentials and a second product group — for shops with two Albis merchant contracts.
Application confirmation to customer, application data to merchant, status updates — overridable per sales channel. Details →
Optional: show the Albis payment method on the product detail page when minimum requirements are met. Details →
Standard Shopware plugin installation, with two migrations for the Albis product groups and configuration defaults.
Pick the ZIP variant for your Shopware version from the downloads section below. Three versions available:
In Shopware admin: Settings → System → Plugins → "Upload plugin". Pick ZIP, upload, then click "Install".
Activate the plugin in the plugin overview. The required migrations (two of them) run automatically — they create the albis_product_group table and configuration defaults.
In the plugin config: activate per sales channel or globally. Without this assignment the payment method does not appear.
API endpoint, username and password — provided by your Albis contact. SSL is required.
In the plugin backend there is a "Test API connection" button. Click it — when the connection works, you are ready for the first test order.
Plugin configuration in the Shopware admin per sales channel or globally — every field explained here.
Full URL of your Albis API endpoint — live or test, depending on what Albis provides. Required.
Entered in the plugin backend. Password protected as type=password. Only Albis can issue these credentials.
Optional — only from v2.5.39 (SW 6.7). Additional credentials for a second Albis merchant contract when Albis runs two separate contracts for you internally.
Via the dropdown you select an Albis product group corresponding to the product-group entry in your Albis account. Transmitted in the application, not visible to customers.
From v2.5: additional product group field — relevant when Albis assigns a different product group per contract.
Optional — included in the leasing rate and sent to Albis. Default: 0.
From which order value (net) additional director data (date of birth, home address) is requested. Freely adjustable.
Should the Albis payment method be shown in the offcanvas cart? Default: off.
Optional BCC address for all Albis order confirmations — for complete internal overview.
API integration, Flow Builder hook-up, in-backend API test, mail templates and optional detail-page display — the features actually shipped in the three plugin versions.
From v2.5.39 (SW 6.7): an additional set of Albis credentials (Username 2 / Password 2) and a second product group in the plugin config. Useful when Albis runs two separate merchant contracts for your shop internally.
New Shopware business event albis.leasing.application.placed — available in Flow Builder after every submitted application. Bundled CreateTagAction automatically tags the order (e. g. albis-pending).
After the application is submitted in checkout, the Albis credit check runs in seconds — answer comes back before the customer leaves the page.
Dedicated "Test API connection" button (endpoint /api/_action/albis-api/verify) — verifies the stored credentials directly against the Albis endpoint, with clear error display on bad data.
Mail templates for application confirmation and status updates to customer and merchant — registered in the Shopware mail manager, customisable per sales channel. Optional BCC for internal overview. Details →
Optionally activatable via plugin config (detailPageDisplay): show the Albis payment method on the product detail page when all minimum requirements are met. Details →
AlbisProductGroup as a standalone Shopware entity with EntityCollection and EntityDefinition — selectable in the backend via sw-entity-single-select.
The Albis API only accepts HTTPS connections with TLS 1.2 or newer. Required before activation.
All storefront and admin strings translated to DE and EN via Shopware snippets — further languages can be added via the standard snippet mechanism.
One ZIP per Shopware major version. Click the download button for the version you need.
For the current Shopware 6.7 line. Full feature set including Contract 2 and Shopware Flow Builder integration.
Size: 118 KB
MD5: a168fd0849920bd2b547dd31d627301e
Stable version for Shopware 6.6 — identical feature set to v2.1.42, compatible with SW 6.6.
Size: 112 KB
MD5: 751db9ef86f6dabdf97f04b0be97ce44
Stable main release for Shopware 6.5 — still maintained. With API test component and AlbisProductGroup entity.
Size: 111 KB
MD5: 5661edcceecbd6d184e393926936070b
On your system: md5sum AlbisLease-v2.5.39-SW6.7.zip — the result must match the MD5 value shown here. If not, the file is corrupted or tampered with — do not install.
State of the plugin source from the ZIP packages offered here.
albis.leasing.application.placed — available in Flow Builder after every submitted applicationAlbisLeasingApplicationPlacedEvent and AlbisLeasingApplicationPlacedAction registeredBusinessEventCollectorSubscriber integrates the event into the Shopware event listCreateTagAction: after the application, automatically tag the order (e. g. albis-pending)TagAware framework event for clean tag assignmentroutes.php instead of routes.xml) — SW 6.7 compliantshopware/core: ~6.6AlbisProductGroup entity incl. EntityCollection and EntityDefinition — selectable via sw-entity-single-selectProductPageSubscriber, OrderPlacedSubscriber, CheckoutConfirmSubscriberAlbisApiService for API communication, AlbisPayment as payment handlerThe questions we get most often about Albis leasing in Shopware — from real customer enquiries.
Yes. The plugin is an interface to the Albis Leasing platform — the actual merchant contract you need to sign directly with Albis Leasing AG. Your Albis contact then provides the API credentials, which you enter into the plugin.
There are three plugin versions, one per active Shopware major line:
Cross-installation (e. g. the SW 6.7 version on a SW 6.6 shop) does not work — the Composer constraints prevent it.
The plugin itself is part of an Albis merchant contract and is free of charge within that relationship. You do not pay a plugin license to Stone & Water — the conditions follow from your Albis contract. If you need an individual setup or customisations, get in touch.
The customer enters their company and (optionally) director data in checkout. The plugin sends them via JSON-RPC to the Albis API. Albis performs the credit check in real time and responds within seconds — with acceptance, rejection or "in review". The status lands on the order and in the status mail to customer and merchant.
From version 2.5.39 (SW 6.7) the plugin config has additional fields for a second set of Albis credentials (Username 2 / Password 2) and a second product group. This is relevant when Albis internally runs two separate merchant contracts for you — the plugin will then send the matching credentials to the Albis API. The UI-level switch for which contract is used per application is not yet part of v2.5.39 and currently needs custom code.
Yes, from v2.5.39 (SW 6.7). The plugin registers the business event albis.leasing.application.placed, which is available in Flow Builder after every submitted application. You can use it e. g. to automatically tag the order with albis-pending or trigger an additional mail.
No. Albis leasing is for business customers (B2B). Private individuals are explicitly excluded — this follows from the Albis contract model, not from the plugin. If you want to offer B2C financing, you need a different provider.
Albis returns the rejection to the plugin, the status on the order is set to "rejected", and both customer and merchant receive a status mail. The order itself remains — you can decide whether to offer the customer an alternative payment method or cancel the order.
Yes, fully. All four mail templates are registered in the Shopware mail manager and can be edited like any other Shopware mail — with Twig, sales channel override and all standard variables plus the Albis-specific ones like {{ albis.application.contract }}. More details →
Every download above has an MD5 checksum. On your system after the download: md5sum AlbisLease-v2.5.39-SW6.7.zip. The result must match the displayed MD5 value — otherwise the file is corrupted or tampered with.
You or we. The installation is a standard Shopware plugin procedure and takes someone familiar with Shopware 20-30 minutes. If you prefer to outsource it: albis@stoneandwater.online — we set up the entire thing, including a test order with a real Albis response.
An older Shopware 5 version (AlbisPayment 5) still exists, but is no longer actively developed — Shopware itself has discontinued official support for SW 5. If you are on SW 5, we recommend migrating to SW 6.7 and the current plugin version v2.5.39.
Symfony services, DAL-compliant data access, Vue 3 in admin. No core patches, no hacks.
Prerequisite: Albis merchant contract. API credentials are provided by your Albis contact.
All contract and customer data is stored in the Shopware database. Credit checks happen at Albis — Albis is the responsible party under GDPR. Data processing agreement with Albis required.
For questions on installation, configuration or for bugs: albis@stoneandwater.online
From plugin upload via Albis API configuration to test order — we handle the entire setup if you want.