Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Besimple Soap Client Laravel Package

reprovinci/besimple-soap-client

A Laravel wrapper for the BeSimple SOAP client that simplifies configuring and using SOAP/WSDL web services in PHP applications. It provides service provider integration and convenient access for building and calling SOAP clients, useful for integrating legacy or third-party SOAP APIs.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Enterprise/B2B integration roadmap. SOAP remains the contract protocol for banking/payments gateways (SEPA, SWIFT-adjacent), insurance claims, payroll/HCM, ERP (SAP PI/PO, Dynamics), telecom billing, and government e-filing. Adopting this package directly underwrites decisions like "can we ship the Partner X integration this quarter?" and "is the Enterprise Integrations epic feasible without commercial middleware?"
  • Contract eligibility and compliance gating. WS-Security (UsernameToken, X.509 signing/encryption, timestamps) is frequently a contractual hard requirement. PHP's native SoapClient cannot do it; this package can. That makes it a "can we legally and technically accept this partner's API spec" decision, not just an engineering preference.
  • Binary/document exchange use cases. MTOM and SwA support opens up invoice ingestion, claims document upload, and PDF/image payloads to partners that refuse base64-in-body. This is a product scope question (do we support attachments in v1?) that the package answers for you.
  • Build vs. buy vs. adopt. The real decision is three-way: build a WS-Security stack in-house (weeks of crypto work, high regression risk), license an iPaaS (MuleSoft/Boomi/Workato — recurring cost, vendor lock-in, slow iteration), or adopt an OSS SOAP client and own its risk. This package represents the third option and is usually the cheapest to reach a working pilot.
  • Integration architecture strategy. Whether the company standardizes on a thin internal SoapClientAdapter interface (with this as one implementation) or lets teams call partner SDKs directly. That's a durable platform decision worth making once, explicitly.
  • Prioritization inputs. Partner revenue × integration blocking-ness vs. the maintenance burden of a low-adoption dependency. Helps rank "unblock Partner A's $Y ARR" above "refactor internal REST clients."

When to Consider This Package

Consider it when:

  • A specific, named partner endpoint requires WS-Security, MTOM, SwA, WS-
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
3mdikram/worldmoneywords
snowsoft/config
itmosoft/laravel-subscriptions
larva/laravel-ai-qwen
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib