Frequently Ask Questions

Here we answer the most frequently asked questions about Pay by Call and its secure IVR payment technology. Our system, with patented 3D Secure, transforms the telephone channel into a reliable, verifiable, and integrable payment environment. It allows you to complete transactions with the same security as an e-commerce platform, without changing your existing infrastructure. If you need more information, our team is available to assist you.

About Pay by Call

Pay by Call is a secure voice payment platform based on IVR technology, designed to help public and private organizations accept payments over the phone with security, compliance, and traceability.

It enables payments in the voice channel without exposing card data to the agent, combining telephony, secure IVR, PSP connectivity, and strong authentication flows.

It is used to turn the phone into a secure, efficient payment channel suited to demanding operating environments.

It solves the problem of insecure, inefficient, or poorly integrated phone payments in organizations where voice remains a key service channel.

It is a payment completed over the phone inside a protected environment where sensitive card data is collected securely and never exposed to the agent.

IVR stands for Interactive Voice Response. In payments, it guides the caller and securely captures the information needed to complete a transaction.

Not in the traditional sense. Pay by Call is positioned as the specialist layer that secures the voice channel and connects it to the client’s PSP.

No. Pay by Call complements the PSP and adds secure phone payment capability as part of an omnichannel strategy.

No. It integrates with the existing contact center, PBX, or CCaaS platform already used by the client.

It is suitable for companies, public administrations, utilities, insurers, BPOs, contact centers, technology platforms, and ecosystem partners.

Security and compliance

Yes. The platform is designed to operate on a secure IVR environment certified to PCI DSS Level 1.

It is the highest PCI DSS compliance level and applies to environments with stringent card-data security requirements.

Yes. The platform is aligned with highly demanding security environments, including those compatible with High category ENS requirements.

It adds security, risk reduction, control of sensitive data, and confidence for clients, auditors, and partners.

Because the voice channel has historically been one of the weakest points in remote payments.

No. In secure Pay by Call flows, the agent does not hear or see the sensitive card information.

They should not be exposed in call recordings when the flow runs inside the secure IVR environment.

Yes. It reduces agent exposure, limits access to sensitive data, and improves control and traceability.

Yes. The platform is designed to record events, statuses, and payment outcomes across the flow.

Yes. Its design supports traceability, control, and operation in auditable environments.

PBC 3DS and strong authentication

PBC 3DS is Pay by Call’s method for bringing PSD2 and 3D Secure strong authentication into the voice channel.

It means applying strong authentication to a phone payment without forcing the user out of the main voice journey.

It is used to strengthen authentication, increase transaction evidence, and reduce fraud, repudiation, and chargebacks in phone payments.

The customer enters the card details in the secure IVR and then completes authentication through the bank’s usual channel while the call remains active.

No. One of its main differentiators is maintaining continuity in the voice channel.

It is designed to provide strong authentication compatible with PSD2 and 3D Secure logic in the voice channel.

Not exactly. The purpose is equivalent, but the experience is adapted to the phone channel.

Yes. It reduces the need to redirect the user to an external web page to authenticate.

Yes. It makes the process more coherent for payments that start in a high-intent phone call.

Yes. It strengthens authentication and improves the quality of transaction evidence.

Yes. By reinforcing authentication, it makes successful disputes more difficult.

Yes. Better authentication and traceability can reduce chargebacks and disputes.

No. It is an optional layer that can be activated according to the client’s policy.

Yes. It can be configured according to amount, service, risk profile, or use case.

Yes. It is especially relevant for high-intent phone calls with human guidance.

Yes. It can form part of automated payment flows depending on service configuration.

Its core differentiator is bringing 3D Secure into the voice channel while preserving continuity of the phone flow.

Yes. The specific strong-authentication method in voice is part of an international patent protection strategy.

Yes. It strengthens authentication, evidence, and traceability.

Yes. It is especially useful where security, control, and evidence are critical.

Modalities and payment experience

It is the family of modalities in which payment is completed during the call with human assistance.

Less channel switching, more guidance, better continuity, and lower abandonment risk.

It is the modality in which the agent transfers the call to the secure IVR at the moment of payment.

It is the modality in which the agent stays on the line guiding the caller without hearing or seeing card data.

In TFA the payment is completed after the transfer to the secure IVR. In LAA the agent keeps guiding the process in real time.

It refers to the automated modalities that allow payments to be processed without human intervention.

It is the modality in which the user calls a dedicated number and completes the payment in an automated way.

It is the modality in which the process starts on the web but is completed through a secure flow connected to the platform.

It is Pay by Call’s own modality integrated into the platform’s secure operating logic.

It is the modality in which the platform generates an automated outbound call to propose and execute the payment.

No. Standard Pay by Link usually moves the user to an external web page. PBC Pay by Link is part of Pay by Call’s operational ecosystem.

Traditional Pay by Link changes channel, while Pay by Agent keeps the payment inside the call.

For high-intent calls, Pay by Agent usually provides a more coherent experience with less friction.

Because it reduces intermediate steps, avoids loss of context, and keeps the user focused.

Because it forces the user to change context, open another environment, and complete more steps.

Yes. Its approach reduces friction and helps close payments inside the same interaction flow.

Yes. It makes the experience more guided, more secure, and more consistent with the channel where payment intent started.

Yes. It is especially useful for regularization, debt recovery, and payments initiated through follow-up calls.

Yes. It enables secure phone payments in sectors where calls remain a key commercial channel.

Yes. These are sectors where the phone remains critical for service, collections, and regularization.

Integrations, cloud, and scalability

Yes. It is designed to work alongside the client’s existing PSP.

Yes. The platform is designed to integrate with existing telephony and service environments.

Yes. It can integrate with cloud contact center platforms.

Yes. It is especially useful for BPOs that want to offer secure phone payments to their clients.

Yes. The platform is prepared for integration with enterprise environments and automated workflows.

Yes. It can work with tokenization through the integrated PSP.

Yes. Tokenization supports repeat transactions and improves the user experience.

Yes. It includes no-agent modalities for automated collections and operational campaigns.

Yes. Its architecture is designed to grow with the client’s volume and needs.

The cloud enables scalability, resilience, less dependence on physical hardware, and more agile deployment.

Yes. The platform is designed to operate on modern, scalable cloud infrastructure.

Better scalability, greater resilience, faster deployments, and lower risk linked to physical infrastructure.

Yes. Its product logic is focused on security, continuity, and control.

Yes. The platform is designed to operate with monitoring and event traceability.

Yes. Its objective is to turn the phone channel into a modern and controlled transactional environment.

Conversational AI

It is the application of artificial intelligence to the voice channel to guide users more effectively and improve interaction.

The platform’s evolution includes conversational AI to improve experience, efficiency, and automation.

No. AI improves the interaction, but sensitive card capture continues to take place inside the secure IVR environment.

It can reduce errors, make interactions more natural, accelerate processes, and improve the user experience.

Yes. Better conversational guidance can reduce abandonment and help complete more operations.

Yes. It can assist with guidance, context, FAQs, and better orchestration of the flow.

Yes. It can make automation feel more natural and improve comprehension and usability.

Yes. It can rephrase instructions, detect doubts, and guide the process more effectively.

Yes, as long as the AI layer remains separate from the secure card-capture layer.

Yes. It helps enrich the value proposition and make it more innovative and competitive.

Benefits for partners

It helps complete the partner’s offer, generate new revenue, and provide secure phone payments as part of an omnichannel proposition.

A partner can open new revenue streams, sell a more complete solution, and win clients that need payment capabilities in the voice channel.

Yes. A more complete omnichannel offer improves the partner’s commercial competitiveness.

Yes. Many enterprise and public-sector clients require omnichannel capabilities and advanced security, so partners without them may be excluded.

Because many buyers do not want partial providers. They want integrated offers that cover web, app, in-person, and phone channels.

They may lose opportunities to competitors with a more complete proposition.

Yes. It adds secure voice payments to an offer that may already cover web, app, or other channels.

PSPs, BPOs, systems integrators, CCaaS platforms, contact center operators, and technology providers.

Yes. It allows the partner to differentiate with a specialist capability that is hard to replicate.

Yes. It also creates commercial, strategic, and positioning value in enterprise and public-sector markets.

Yes. Having a secure omnichannel offer can open doors that would otherwise remain closed.

Yes. It is especially suitable for indirect models, white-label offerings, integrations, and technology alliances.

They are looking for security, compliance, integration, operational continuity, and a coherent experience in the voice channel.

Its main differentiator is combining PCI DSS Level 1 secure IVR, a strong fit for demanding environments, integration with the existing ecosystem, and PBC 3DS as native 3D Secure in voice.

Because it turns the phone into a modern, secure, omnichannel payment channel prepared to evolve with strong authentication and conversational AI.