Soft Space

• Organizations that mandate publicly available SOC 2/ISO 27001 attestations and cannot proceed without them (these were not clearly documented in the public sources reviewed).
• Buyers that require self-serve onboarding globally with transparent pricing and comprehensive public developer documentation (alternatives may be preferable).
• Buyers seeking a full POS suite out of the box without additional integration (hardware-led ecosystems may be preferable).

A Fasstap landing page indicated PIN entry for transactions above a specified threshold was planned; buyers should confirm current capability and certification status for PIN entry in their target markets.

Soft Space states deployments across multiple markets, but public SLOs, uptime metrics, and incident history were not prominently published in the materials reviewed.

• PCI MPoC/SPoC references are the primary public compliance anchors.
• SOC 2 and ISO 27001 documentation were not clearly found in public sources and should be requested by buyers if required.

Common SoftPOS program constraints apply: device compatibility variation, differing scheme rules by country, and partner acquirer processes that affect onboarding timelines.

• Compliance-focused messaging: Soft Space emphasizes PCI SSC-related certifications (MPoC and earlier SPoC references), which are relevant for SoftPOS and secure PIN entry.
• Partner and acquirer delivery model: public announcements document partnerships with payment stakeholders in certain markets.
• Claimed multi-OS support: partner materials reference Android, iOS, and other OS support in some programs.

• Stripe: broader public developer documentation, self-serve onboarding, and a unified online and in-person payments stack in many markets.
• Square/Clover: turnkey merchant operations and POS feature sets for SMB customers.

G2’s listing for "Softspace" appears to refer to a different entity/product and not the payments vendor, creating a risk of mistaken identity.

Implication: Public software review platforms may not provide robust review coverage for the vendor under the correct listing. Buyers should prioritize references such as bank/acquirer customer references, certification artifacts, partner case studies, and direct customer contacts.

The vendor’s website contains partner testimonials from executives. These are curated and useful for understanding positioning but are not independent user reviews.

Public merchant-level discussions were limited in the sources reviewed, which is common for regulated payments infrastructure vendors that sell primarily via banks and acquirers.

Public employer review sites include employee reviews with mixed signals. Some reviews cite attrition in specific roles, management and process concerns, and benefits/flexibility issues. Employee sentiment can indicate execution risk that may affect implementation and support quality in enterprise deployments.

Announcements and partner selections indicate the vendor is chosen for SoftPOS / tap-to-phone enablement, PCI certifications, white-label delivery capabilities, and claimed multi-OS support.

• Slower product iteration due to compliance-heavy roadmaps.
• Support and operational friction in bank-led deployments.
• Pricing competitiveness versus alternatives.
• Geographic coverage and local acquiring limitations compared with global processors.

The vendor states a customized SoftPOS merchant application was developed with an Australian payments customer to enable Tap to Pay on iPhone for that customer’s merchants.

Critical evaluation: This supports the vendor’s white-label delivery narrative but does not provide independent ROI or operational metrics.

The vendor states that Fasstap received MPoC Solution Provider certification and that a subsidiary performed an early live deployment of an MPoC-certified solution.

Critical evaluation: Certification is a relevant compliance signal. Buyers should verify certification scope, attestation listings, and alignment between their intended deployment architecture and the certified configuration.

Vendor communications and historical coverage reference deployments or target markets including retail (convenience stores, pharmacies), aviation/inflight, transit/logistics, and general SME merchant acceptance.

• Decision makers: Head of Payments, Head of Acquiring, CTO/CISO (for compliance-heavy programs), Product Director (merchant acceptance), Partnerships.
• End users: merchant staff, field sales representatives, pop-up/event sellers, service technicians.

• Requirement for hardware-minimizing acceptance at scale.
• Need for white-label and partner deployability.
• Existence of compliance capabilities or need for a partner with a track record in SoftPOS and card-scheme certification.