GITNUXSOFTWARE ADVICE
Finance Financial ServicesTop 10 Best Qr Code Payment Services of 2026
Compare top qr code payment services and what they fit best for merchants, with tradeoffs noted for checkout and reporting.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
SumUp is the best overall choice for small merchants that want quick QR creation and simpler back-office reconciliation because its dashboard ties QR issuance to consolidated settlement and reporting, while Worldpay fits enterprises that already run Worldpay workflows since QR transactions are handled inside the same authorization and settlement lifecycle.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
SumUp
Merchant QR creation inside the operational dashboard, paired with consolidated settlement and operational reporting for QR campaigns.
Best for: Fits when merchants need fast QR checkout adoption and developers want limited integration surface.
Mollie
Editor pickWebhook-based transaction status updates that drive automated order state changes for QR payments.
Best for: Fits when teams need QR payment orchestration via API and webhook-driven order updates.
Worldpay
Editor pickQR transaction processing routed through Worldpay’s authorization and settlement workflow rather than a standalone QR-only engine.
Best for: Fits when merchants already use Worldpay interfaces and need QR transactions governed by the same authorization, status, and settlement controls.
Comparison Table
SumUp
specialistEuropean SMB payment provider offering QR code payment acceptance for small merchants.
Merchant QR creation inside the operational dashboard, paired with consolidated settlement and operational reporting for QR campaigns.
SumUp packages QR acceptance with acquiring operations so QR code issuance can be handled through the same merchant administration area. Its QR approach is primarily suited to merchant-presented checkout rather than developer-driven QR payload generation. The service covers core payment lifecycle operations like authorization and post-payment adjustments through one console.
- +Quick QR code issuance for merchant-presented scenarios with minimal setup steps
- +Transaction reporting consolidates QR payments into a single merchant back office
- +Refund and reversal flows are exposed through the same operational console
- +Works well for low-to-moderate QR throughput without custom orchestration
- –Limited depth for developers needing custom dynamic QR payload control
- –Webhook granularity may be insufficient for strict reconciliation automation
- –Supports fewer advanced QR lifecycle options than enterprise payment stacks
- –Scaling high-volume QR issuance can require process changes in operations
Best for: Fits when merchants need fast QR checkout adoption and developers want limited integration surface.
Mollie
specialistEuropean payment provider supporting QR code payment methods for online merchants.
Webhook-based transaction status updates that drive automated order state changes for QR payments.
Mollie’s core QR payment workflow centers on creating a payment intent via API, presenting a QR code to the customer, and then monitoring authorization and completion status using webhook events. The integration fit is strongest for teams that already process orders and want the gateway to act as a payment state machine with clear status callbacks. Administration and governance show up through event-driven controls that let operations react to payment outcomes without scraping logs or polling. A practical tradeoff is that QR code generation and presentation depend on how the merchant-presented or consumer-presented flow is implemented in the checkout experience, so front-end work is still required.
Mollie works well when a single backend needs to drive QR payments across multiple POS or web checkout surfaces while keeping transaction lifecycles synchronized through webhooks. For reconciliation, Mollie’s event delivery supports automated workflows that map payment identifiers back to internal order IDs. That reduces manual matching compared with approaches that only provide periodic settlement files and no real-time transaction status stream.
- +API-first payment creation with consistent status and lifecycle handling
- +Webhook events support automated reconciliation and order-state updates
- +Refund workflows keep QR transaction management inside the same surface
- +Sandbox supports end-to-end integration testing with realistic callbacks
- –QR presentation requires front-end integration work in the checkout experience
- –Webhook design requires careful idempotency handling for duplicate delivery
Marketplace engineering teams
Generate QR for split orders
Lower manual payment matching
Retail POS developers
Merchant-presented QR at checkout
Faster acceptance at counters
Show 2 more scenarios
E-commerce operations teams
Reconcile QR payments automatically
Reduced reconciliation delays
Operations routes webhook callbacks into accounting and customer support workflows using internal IDs.
Platform onboarding teams
Standardize payment flows across merchants
Consistent payment operations
A single integration pattern handles QR payment creation and refund operations per merchant account.
Best for: Fits when teams need QR payment orchestration via API and webhook-driven order updates.
Worldpay
enterprise_vendorGlobal payment processing service supporting QR code payment acceptance for enterprises.
QR transaction processing routed through Worldpay’s authorization and settlement workflow rather than a standalone QR-only engine.
Worldpay processes QR code payment transactions through its merchant acquiring and payment orchestration services used in account-based payment flows. Merchants can generate QR code payloads that support in-store merchant-presented and app-assisted consumer journeys depending on market availability.
The integration focus centers on payment authorization, status updates, and settlement handling through Worldpay’s standard gateway and acquiring interfaces. Operational control depends on how Worldpay exposes callbacks, reconciliation data, and refund workflows for QR-originated transactions in each setup.
- +Works within Worldpay’s acquiring and payment authorization lifecycle
- +Supports QR code transaction status handling via standard notification patterns
- +Handles settlement and refund workflows tied to captured transactions
- +Integration aligns with common gateway and acquiring customer implementations
- –QR code payload options depend on market and specific contract configuration
- –Dynamic QR flows require stronger back-end orchestration than static codes
- –Webhooks and reconciliation behavior can vary by transaction routing
- –Requires attention to duplicate-payment prevention rules across retries
Best for: Fits when merchants already use Worldpay interfaces and need QR transactions governed by the same authorization, status, and settlement controls.
Adyen
enterprise_vendorEnterprise payment platform supporting QR code payment methods across global markets.
Webhook-led transaction status processing with operational tooling that aligns QR events to the same reconciliation model used elsewhere.
Adyen’s QR payments fit merchants that already run card and wallet flows through Adyen and want QR to behave like the rest of the portfolio. The API-first model supports request-based initiation and callback-driven transaction status handling, which helps keep checkout logic deterministic across channels. Operations workflows are built around transaction events, reconciliation support, and back-office tooling used by larger payment operations teams.
- +Single transaction lifecycle across QR and other payment methods
- +Webhook-driven status updates reduce client polling and race conditions
- +Operational tooling supports reconciliation workflows for payment teams
- +Extensible API surface for payment method configuration and routing
- –QR-specific setup needs careful backend idempotency and retry logic
- –Implementation effort is higher than lightweight QR-only aggregators
- –Status edge cases still require explicit webhook handling
- –Tight coupling to Adyen flows can slow experimentation with payload variants
Marketplace and platform engineering teams
Merchant QR payments with backend reconciliation
Lower dispute workload and clearer ledgers
Omnichannel retail POS teams
In-store QR acceptance with consistent lifecycle
Fewer mismatches across channels
Show 2 more scenarios
Enterprise payment operations teams
Governed payment behavior and monitoring
Faster incident triage
Operations can apply configuration discipline and track event outcomes through unified transaction tooling.
Digital commerce backend teams
High volume QR checkout orchestration
More stable checkout under load
Backends can manage throughput with request-based initiation and deterministic status updates.
Best for: Fits when payments engineering teams need API-led QR integration and strong operations controls.
Stripe
enterprise_vendorPayment infrastructure company supporting QR code payment flows for online and physical commerce.
Webhook-driven payment lifecycle updates tied to Payment Intents for reconciliation without periodic scraping.
Stripe processes QR code payments by routing transactions through its Payments API, with QR flows typically supported via Stripe Checkout, Payment Links, and invoice-driven payment experiences. It differentiates through a broad payment API surface that includes payment intent handling, idempotency controls, and webhook-based transaction status updates.
- +Webhooks deliver granular payment lifecycle events for QR reconciliation
- +Idempotency keys reduce duplicate-payment risk during retries
- +Payment Intents standardize authorization and status polling patterns
- +Dashboard configuration supports audit-friendly operational workflows
- –QR-specific payload and code-generation controls depend on integration approach
- –More engineering effort is needed for fully custom merchant-presented flows
- –Settlement and refund workflows require webhook-driven implementation discipline
- –Complex multi-account setups can require careful API key and webhook scoping
Best for: Fits when teams already build on Stripe and need QR-capable payment orchestration via webhooks.
BharatPe
specialistIndian merchant-focused payment company providing interoperable QR code payment acceptance.
Merchant console workflow that ties QR acceptance activity to transaction visibility for reconciliation at scale.
BharatPe’s QR acceptance is designed around merchant-presented workflows, where the QR payload is tied to payment intent and the merchant can track outcomes. The service supports operational reporting that helps match scans to completed transactions and surface failures. For teams expanding from one store to many, BharatPe’s merchant operations model reduces the need to rebuild acceptance and monitoring per location.
- +Merchant operations and transaction monitoring support daily reconciliation workflows
- +Centralized QR acceptance helps multi-outlet deployments stay consistent
- +Integration path supports wiring QR acceptance into business systems
- +Status visibility reduces manual chase for failed or pending payments
- –Deep QR payload customization is limited compared with fully custom QR engines
- –Dynamic QR patterns require tighter lifecycle handling in the merchant system
Retail ops teams
Track scans across multiple outlets
Faster reconciliation and fewer disputes
Payments engineering teams
Integrate QR acceptance into systems
Lower manual payment status handling
Show 1 more scenario
Store managers
Deploy QR acceptance quickly
More consistent in-store payments
Merchant-focused setup supports deploying QR acceptance without building custom payment operations.
Best for: Fits when retail groups want centralized QR acceptance monitoring across multiple outlets.
Cashfree
specialistIndian payment provider offering QR code payment APIs and merchant collection tools.
Transaction status callbacks and reconciliation references designed for QR scan to settlement matching.
Cashfree provides QR code payment acceptance with APIs for generating payment QR payloads, initiating transactions, and tracking outcomes. Its distinct angle is developer-first orchestration across checkout, webhook-based reconciliation, and refund workflows tied to the same transaction references.
- +API coverage for QR payload creation, transaction initiation, and status polling
- +Webhook-driven reconciliation reduces manual matching for QR scans
- +Refund workflows map back to original transaction references
- +Strong operational visibility through transaction-level reporting
- –Requires careful webhook verification and idempotency to prevent duplicate processing
- –QR payload formats and edge behaviors need implementation testing per device wallet
- –Certain reconciliation steps rely on consistent merchant reference handling
- –Operational governance takes effort when multiple teams share credentials
Best for: Fits when dev teams need QR payment APIs plus webhook reconciliation for high-throughput checkout flows.
Razorpay
specialistIndian payment platform offering dynamic QR code payments for businesses and merchants.
Dynamic QR code issuance backed by payment object IDs that drive automated reconciliation through webhooks.
Razorpay fits merchants that need QR code payment workflows tied into an existing payment stack and reconciliation layer. The service centers on programmable payment initiation with account-linked payment objects, then drives completion signals via status callbacks and webhooks for automation.
- +Webhook and callback events map clearly to payment lifecycle states
- +Dynamic QR generation supports operational tracking and better fraud posture
- +APIs cover payment creation, status retrieval, and refund flows
- +Strong dashboard tooling for monitoring disputes, failures, and settlements
- –QR acceptance setup can require careful handling of idempotency and retries
- –Merchant-presented QR payload customization is limited versus fully custom QR generation
- –Operations teams often need internal playbooks for webhook reconciliation edge cases
- –Complex multi-channel deployments can require deeper integration work
Best for: Fits when a mid-market team needs QR payment automation through APIs, webhooks, and reconciliation.
Alipay
enterprise_vendorChinese mobile payment platform that pioneered QR code payments for merchants and consumers worldwide.
Alipay QR payment routing into Alipay’s account-based settlement flow for reconciliation and lifecycle management.
Alipay is a QR-code payment service that fits merchants needing strong adoption across Alipay’s consumer base. It supports merchant-presented and account-linked QR flows that route payments into Alipay’s settlement and reconciliation processes.
- +High consumer recognition when shoppers already use Alipay for QR payments
- +Transaction lifecycle support includes payment confirmation and refund workflows
- +Reconciliation can be driven from transaction status updates and settlement outputs
- +Works well for in-store and app-adjacent checkout experiences using QR payloads
- –Integration depth varies by merchant account configuration and regional availability
- –Callback and reconciliation design requires careful handling to prevent missed status changes
Best for: Fits when merchants target Alipay users and need QR payments with transaction status tracking and refund handling.
Klarna
specialistEuropean payment service offering QR code checkout for retail merchants.
Order lifecycle alignment ties QR payment status to Klarna’s authorization and confirmation flow rather than standalone QR tracking.
Klarna is a payments provider known for credit-led checkout and consumer-focused commerce flows that can pair with QR-based payment experiences in merchant channels. It supports QR payment acceptance by tying payment intent creation to Klarna’s authorization and confirmation model, so merchants can keep status tracking aligned with Klarna order lifecycle events.
- +QR payment outcomes stay aligned with Klarna order lifecycle events
- +API integration fits merchants already building Klarna checkout flows
- +Strong consumer credit experience reduces friction for eligible shoppers
- +Status delivery supports operational reconciliation for payment success and failure
- –QR acceptance coverage depends on Klarna market availability and program scope
- –Dynamic QR behaviors and amount encoding are not as developer-transparent as pure gateway QR engines
- –Refund and reversal flows may require additional Klarna-specific workflow wiring
- –Requires governance around Klarna order identifiers to prevent mismatched reconciliation
Best for: Fits when merchants already run Klarna checkout and need QR payments tied to Klarna order status.
Conclusion
After evaluating 10 qr code payment, SumUp stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Qr Code Payment
QR code payment services covered here include Adyen, Alipay, BharatPe, Cashfree, Klarna, Mollie, Razorpay, Stripe, SumUp, and Worldpay. Each provider takes a different path to QR scan initiation, payment lifecycle updates, and reconciliation.
Some platforms center webhook-driven transaction status processing, while others tie QR outcomes into existing authorization and order lifecycles. Merchant and developer teams can compare how each service handles idempotency, delivery timing, and the operational controls needed for clean settlement.
How Qr Code Payment services handle scan initiation and payment lifecycle reconciliation
QR code payment is a payment flow where a QR code payload triggers payment authorization and later status updates that reconcile scans to settlement and refunds. Providers differ in whether they drive status changes through webhooks, callbacks, or operational dashboards that aggregate QR activity for merchant back offices.
Adyen and Mollie both use webhook-based transaction status updates that support automated order-state changes and reduce reliance on periodic polling. Stripe and Razorpay similarly align payment lifecycle reporting to payment objects and webhook events so teams can reconcile QR payments to a specific transaction lifecycle with idempotency controls.
QR payment reconciliation signals, payload controls, and automation depth
QR code payment deployments succeed when the scan outcome turns into a measurable payment lifecycle event that the merchant system can reconcile to authorization, settlement, and refunds. Services that publish webhook or callback status tied to a payment object reduce manual matching and prevent order state drift after a QR scan.
Webhook-led transaction status that maps to a payment lifecycle
Adyen and Mollie provide webhook-driven status updates that align QR transaction processing with a consistent reconciliation model. Stripe also uses webhook-driven lifecycle updates tied to Payment Intents so QR payment outcomes can reconcile without periodic scraping.
Idempotency and retry behavior for scan outcomes delivered more than once
Razorpay issues dynamic QR codes backed by payment object IDs and supports automated reconciliation through webhooks, which still requires careful idempotency handling. Stripe includes idempotency keys to reduce duplicate-payment risk when retries occur during QR flow delivery.
Reconciliation support that connects QR events to refunds and lifecycle workflows
Alipay routes QR payments into its account-based settlement flow, which supports transaction lifecycle tracking including payment confirmation and refund workflows. Worldpay routes QR transactions through its authorization and settlement workflow so QR status handling follows the same acquiring and payment lifecycle controls.
Integration surface for QR initiation, from code issuance to checkout orchestration
Cashfree provides API coverage for QR payload creation, transaction initiation, and status polling, with transaction status callbacks designed for scan-to-settlement matching. Klarna aligns QR payment status with Klarna’s authorization and confirmation flow, which fits merchants that already build Klarna checkout.
Developer control over dynamic versus static QR payload and customization limits
Razorpay supports dynamic QR code issuance tied to payment object IDs, which improves operational tracking but limits merchant-presented payload customization versus fully custom QR generation. BharatPe offers centralized QR acceptance monitoring, but deep QR payload customization is limited compared with fully custom QR engines.
Operational visibility for multi-outlet QR acceptance and settlement reporting
BharatPe provides a merchant console workflow that ties QR acceptance activity to transaction visibility for reconciliation at scale. SumUp offers merchant QR creation in the operational dashboard and consolidates settlement and operational reporting for QR campaigns.
Choose QR payment plumbing based on lifecycle signals and the control plane needed
The main fork is whether the merchant system must consume QR outcomes through webhooks and payment-object events or whether daily operations can rely on consolidated dashboards. Adyen, Mollie, Stripe, and Cashfree focus on webhook-driven reconciliation, which fits engineering teams that want automated order state changes after QR scans.
Map QR scan outcomes to the status delivery model the merchant system will consume
If the merchant stack expects event-driven updates, prioritize Adyen, Mollie, Stripe, or Cashfree because they use webhook or callback-driven transaction status processing that reduces reliance on polling. If the merchant team needs operational visibility more than engineering orchestration, SumUp and BharatPe provide dashboard workflows that consolidate QR acceptance activity for back-office reconciliation.
Pick a reconciliation anchor that matches refunds, settlement, and lifecycle ownership
If QR payments must follow a platform-owned lifecycle with refund workflows, Alipay routes QR payments into its account-based settlement flow. If QR transactions must follow the same acquiring workflow as other payment methods, Worldpay and Adyen route QR processing through their broader authorization and settlement lifecycle.
Set expectations for QR payload control in merchant-presented scenarios
For dynamic issuance with payment-object tracking, Razorpay emphasizes dynamic QR generation and webhook reconciliation but keeps merchant-presented payload customization limited versus fully custom QR engines. For operations-first deployments, BharatPe supports centralized QR acceptance monitoring but provides limited deep QR payload customization.
Design for duplicate deliveries and delayed status transitions
Where QR flows depend on webhooks, require idempotency and retry-safe backend handling because duplicate webhook deliveries can occur even when the payment status is correct. Stripe reduces duplicate-payment risk with idempotency keys, while Adyen and Mollie still require backend idempotency and retry logic to handle QR-specific setup and delivery timing.
Check whether your frontend must orchestrate QR presentation
If the merchant already owns checkout UI orchestration, Mollie and Adyen can fit well, but QR presentation still needs frontend integration work in the checkout experience. If QR presentation must be fast to adopt with limited developer surface area, SumUp emphasizes quick QR code issuance through the operational dashboard.
Align QR payments with an existing order lifecycle when the merchant runs partner checkout
If merchants already build Klarna checkout, Klarna aligns QR payment status to Klarna’s authorization and confirmation flow rather than standalone QR tracking. If merchants already use Worldpay interfaces, Worldpay keeps QR transactions governed by Worldpay’s authorization and settlement controls so QR status handling follows standard notification patterns.
Who should buy Qr Code Payment services from this set
Engineering teams should focus on providers whose QR scan outcomes arrive as structured events tied to payment lifecycles. Operations teams should focus on providers that centralize QR acceptance monitoring and make reconciliation visible without deep engineering work.
Payment engineering teams building API-led QR integration
Adyen, Mollie, Stripe, and Cashfree support API and webhook-driven status updates so teams can reconcile QR transactions into their order state machine without polling.
Merchants running multi-outlet operations that need consolidated QR acceptance visibility
BharatPe ties QR acceptance activity to transaction visibility in a merchant console so groups can run daily reconciliation workflows across multiple outlets. SumUp consolidates QR settlement and operational reporting into a single merchant back office.
Merchants targeting shoppers who already pay via Alipay QR flows
Alipay routes QR payments into an account-based settlement flow that supports transaction lifecycle tracking and refund workflows aligned to how Alipay manages accounts.
Merchants that already run Klarna checkout and want QR outcomes tied to order lifecycle
Klarna aligns QR payment outcomes to Klarna’s authorization and confirmation flow so QR scan results map to Klarna order status rather than standalone QR tracking.
Mid-market teams needing automated QR issuance with payment-object tracking
Razorpay supports dynamic QR code issuance backed by payment object IDs and webhook reconciliation, which helps automate lifecycle tracking for QR scans.
Common Qr Code Payment buying mistakes
Many QR payment implementations fail when teams underestimate how status delivery timing affects reconciliation and how duplicate events can corrupt order states. Others fail by assuming QR payload customization options are unlimited when the provider expects defined patterns for QR generation and lifecycle handling.
Treating webhook or callback status updates as strictly one-time deliveries
Adyen, Mollie, Razorpay, and Cashfree rely on webhook or callback-driven processing, so duplicate deliveries can occur and backend idempotency and retry logic must be built. Stripe reduces duplicate-payment risk with idempotency keys, but reconciliation logic still needs to tolerate retries and out-of-order status.
Choosing QR payload control based on assumptions instead of merchant-presented requirements
Razorpay’s dynamic QR issuance improves operational tracking but keeps merchant-presented payload customization limited versus fully custom QR generation. BharatPe limits deep QR payload customization compared with fully custom QR engines, so merchant system requirements should be validated against those constraints.
Underestimating the integration work needed to present QR codes in the checkout experience
Mollie and Adyen use webhook-driven transaction status updates, but QR presentation still requires frontend integration work in the checkout experience. SumUp offers dashboard-driven QR issuance that reduces frontend integration effort, so frontend ownership should be considered before committing.
Ignoring how refunds and lifecycle ownership differ across QR routing models
Alipay’s QR payments route into its account-based settlement flow, so refund and lifecycle handling follows that model rather than an external standalone QR tracker. Worldpay routes QR transactions through its authorization and settlement workflow, so reconciliation should align to Worldpay’s standard lifecycle controls.
Picking a provider for QR acceptance monitoring but losing reconciliation granularity needed for automation
SumUp and BharatPe centralize QR acceptance monitoring and reporting for reconciliation visibility, but webhook granularity can be insufficient for strict reconciliation automation. If automated order-state changes must be immediate and consistent, webhook-led providers like Cashfree, Mollie, or Stripe fit better.
How analysts checked the QR payment providers in this guide
Analysts opened the original publication and copied the figures shown next to the passages that describe specific provider capabilities. Analysts compared each copied figure with the provider documentation and changelog, and they used an independent review when one was cited for a claim.
Analysts kept each figure only when it matched the documentation and included an external benchmark only when that benchmark was the cited source. Coverage focused on QR scan initiation and how transaction status signals support reconciliation and lifecycle workflows across engineering and operational use.
Frequently Asked Questions About Qr Code Payment
How do Adyen and Mollie handle QR transaction status without polling?
Which service providers are better for developer onboarding with a QR payment API and webhooks?
What breaks if a merchant treats QR codes as static artifacts while using dynamic workflows?
How do merchants implement SSO and RBAC controls for QR payment administration?
How should organizations migrate existing QR payment data models when switching providers?
Where does Worldpay tend to fall short for merchants that need full control over QR payload creation?
How do refunds and reversals behave differently across Klarna and BharatPe QR integrations?
When do merchant-presented QR flows require extra front-end work in services like SumUp and Adyen?
Which provider fit signals point to stronger automation for reconciliation after QR scans?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
- Finance Financial ServicesTop 10 Best Payment Services of 2026
- Technology Digital MediaTop 10 Best Qr Code Generator Services of 2026
- Finance Financial ServicesTop 10 Best Credit Card Payment Merchant Services of 2026
- Finance Financial ServicesTop 10 Best E Payment Software of 2026
- Marketing AdvertisingTop 10 Best Qr Code Tracking Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Finance Financial Services alternatives
See side-by-side comparisons of finance financial services tools and pick the right one for your stack.
Compare finance financial services tools→