ValPay is an embedded payments platform built for software companies rather than bolted onto one. It runs a PayFac-as-a-Service model, which means it absorbs the underwriting, compliance, and regulatory work that would otherwise land on you or on us. Car rental is one of the verticals it serves directly, alongside marine and hospitality.
Through the RentWorks Plus integration, a deposit, a rental charge, and a refund all happen against the agreement they belong to, instead of on a terminal someone has to reconcile later. Card data sits with a PCI-DSS Level 1 provider rather than in a drawer at the counter: tokenized workflows are designed so the sensitive card number is held by the payment provider and the rental record keeps a token instead.
ValPay processes in USD, CAD, EUR, GBP, and AUD, and supports in-person, online, and omnichannel acceptance, with turnkey compliance plus real-time fraud and risk monitoring so the certification burden is not something your locations carry alone.
ValPay is a third-party payment provider with its own agreement and rates, quoted separately from the platform. Which currencies apply to your locations, which card brands and card-present devices are enabled, and your exact PCI scope and responsibilities are confirmed during implementation.
No. ValPay is a third-party payment provider with its own agreement and rates, quoted separately from the platform. Your proposal lists what the payment side costs so there is no assumption left in the deal.
With the payment provider, not in your records. Tokenized workflows are designed so a PCI-DSS Level 1 provider holds the sensitive card number while the rental record keeps a token it can charge against.
ValPay processes in USD, CAD, EUR, GBP, and AUD, and supports in-person, online, and omnichannel acceptance. Which currencies, card brands, and card-present devices are enabled for your locations is confirmed during implementation.
It reduces the surface, it does not erase the obligation. ValPay provides turnkey compliance plus real-time fraud and risk monitoring, but your exact PCI scope and responsibilities depend on how you accept payments and are confirmed during implementation.
Bluebird supports the RentWorks Plus side of the connection and ValPay supports the payment product. Your implementation plan names the escalation path for both, so nobody spends a morning guessing which vendor owns the problem.
ValPay is an embedded payments platform built for software companies rather than bolted onto one. It runs a PayFac-as-a-Service model, which means it absorbs the underwriting, compliance, and regulatory work that would otherwise land on you or on us. Car rental is one of the verticals it serves directly, alongside marine and hospitality.
Through the RentWorks Plus integration, a deposit, a rental charge, and a refund all happen against the agreement they belong to, instead of on a terminal someone has to reconcile later. Card data sits with a PCI-DSS Level 1 provider rather than in a drawer at the counter: tokenized workflows are designed so the sensitive card number is held by the payment provider and the rental record keeps a token instead.
ValPay processes in USD, CAD, EUR, GBP, and AUD, and supports in-person, online, and omnichannel acceptance, with turnkey compliance plus real-time fraud and risk monitoring so the certification burden is not something your locations carry alone.
ValPay is a third-party payment provider with its own agreement and rates, quoted separately from the platform. Which currencies apply to your locations, which card brands and card-present devices are enabled, and your exact PCI scope and responsibilities are confirmed during implementation.
No. ValPay is a third-party payment provider with its own agreement and rates, quoted separately from the platform. Your proposal lists what the payment side costs so there is no assumption left in the deal.
With the payment provider, not in your records. Tokenized workflows are designed so a PCI-DSS Level 1 provider holds the sensitive card number while the rental record keeps a token it can charge against.
ValPay processes in USD, CAD, EUR, GBP, and AUD, and supports in-person, online, and omnichannel acceptance. Which currencies, card brands, and card-present devices are enabled for your locations is confirmed during implementation.
It reduces the surface, it does not erase the obligation. ValPay provides turnkey compliance plus real-time fraud and risk monitoring, but your exact PCI scope and responsibilities depend on how you accept payments and are confirmed during implementation.
Bluebird supports the RentWorks Plus side of the connection and ValPay supports the payment product. Your implementation plan names the escalation path for both, so nobody spends a morning guessing which vendor owns the problem.