DOCSEARCHbyAlgolia
Submit Docs

Wallee Documentation

website·Indexed 31 days ago

https://wallee-whitelabel-documentation.staging-wallee.com

Documentation for Wallee's payment processing platform, including POS troubleshooting, terminal handling, and e-commerce plugin integrations for Magento 2 and Shopware 6.

Tokens
75.5K
Snippets
160
Records
606
Agent score
50%

What's inside Wallee

  1. Overview of wallee join partner platform

    wallee join is a partner platform for integrated payments designed for affiliates, agencies, system integrators, SaaS platforms, and Independent Software Vendors (ISVs). It allows partners to embed payment acceptance (e-commerce checkouts, POS terminals, unattended payments) into their own products or refer merchants to wallee. wallee handles the regulatory overhead, including KYC, AML, PSD2 compliance, risk, and chargeback management.

  2. Overview of Click to Pay

    Click to Pay is a unified wallet standard introduced by major credit card networks to streamline online checkouts. It allows consumers to use pre-saved cards instead of manually entering credit card details for every purchase. Security is handled via scheme token technology, ensuring that sensitive card data (like card numbers or expiration dates) is not exchanged or stored during the transaction.

  3. Overview of wallee SoftPOS for Android

    wallee SoftPOS allows a standard Android device to be used as a card payment terminal without additional hardware. The integration is implemented via the Terminal API, an Android library that provides both Kotlin coroutine and Java callback APIs. The SDK interacts with the on-device SoftPOS service and organizes operations into four primary domains: payments, configuration, batch, and identification.

  4. Overview of the Merchant Applications API

    The Merchant Applications API manages the KYC (Know Your Customer) data of onboarding merchants, including company details, legal forms, beneficial owners, bank details, and product/pricing context. Applications are structured into steps that can be updated individually. The process typically ends with a legal confirmation by the merchant via a hosted submission flow.

    Base Path: /api/v2.0/onboarding/merchant-applications Required Permission: JOIN_PROGRAM_ACCESS

  5. Overview of wallee omnichannel payment processing

    wallee is a PCI DSS Level 1 compliant payment platform that provides a single API, portal, and contract for processing payments across three main channels: E-commerce (via hosted payment pages or iframes), In-store (integrated card terminals), and Unattended (vending machines, kiosks, and charging stations).

  6. Overview of ReconHub payment reconciliation

    ReconHub is an automated payment reconciliation platform by Abrantix integrated with the Wallee Portal. It aggregates transaction and financial data from multiple sales channels (POS, e-commerce, marketplaces), processors, banks, and ledgers to streamline transaction-level matching. Key capabilities include:

    • All-Channel Reconciliation: Matches data per transaction across various payment types and currencies.
    • Exception Handling: Uses a rules engine to detect and flag mismatches for review.
    • Ledger Posting: Exports matched payments as accounting entries to ERP systems like SAP, Sage, Abacus, and MS Dynamics.
    • Analytics: Provides insights into fee structures, cash flow, and outstanding receivables.
    • Integration: Connects via API or batch files (CSV, XML, JSON, Excel, SFTP).

  7. Overview of Wallee integration for Peppershop

    Peppershop is a Swiss online store system that integrates with the Wallee Portal terminal. This integration supports an omnichannel setup, allowing merchants to run an online store and process in-store sales via a connected POS. The extension is a partner-built plugin developed and maintained by Peppershop, while Wallee handles the payments, transactions, and account management.

  9. Overview of Wallee Portal extension for Magento 2

    The Wallee Portal extension for Magento 2 (Adobe Commerce) enables payment processing by synchronizing payment methods configured centrally in the Wallee space into the Magento store. While configuration is centralized, transaction management—including captures, voids, and refunds—should be performed directly from the Magento backend to ensure proper synchronization.

  10. Overview of Pingen Print integration for wallee

    Pingen Print is a cloud-based printing and mailing service integrated with wallee to automate the PDF printing and postal dispatch of invoices, reminders, and packing slips. Printing jobs are triggered via web requests and sent to supported providers based on default or custom printer configurations assigned per document type or connector. Key capabilities include seamless integration with pingen.com, connector-level printer assignment, automatic triggering based on transaction states (e.g., Completed or Fulfill), and built-in retry logic for failed jobs.

  11. Overview of Wallee Portal plugin for Shopware 6

    The Wallee Portal plugin for Shopware 6 integrates payment processing into a Shopware store. It supports customer payments via iFrame, lightbox, or hosted payment pages. Payment operations such as captures, voids, and refunds are managed directly from the Shopware backend. Payment methods are configured centrally in the Wallee space and synchronized into Shopware, allowing new methods to be added without modifying the shop configuration.

  12. Overview of the wallee API merchant onboarding flow

    The wallee Web Service API (v2.0) allows platforms to embed merchant onboarding. The process follows these four primary steps:

    1. Create a partnership: Establish the relationship for the merchant (Affiliate, ISV, or existing account).
    2. Submit KYC data: Create a merchant application and prefill it with known company data to reduce friction.
    3. Hand over to the merchant: Provide the merchant with a hosted submission URL to review and legally confirm the application.
    4. Track status: Monitor the application until the account becomes active via polling or webhooks.