Porting Telephone Numbers from Aircall to Paytia

Overview

This article explains how to port existing Aircall telephone numbers to Paytia so Paytia sits in front of Aircall for secure payment card capture.

This configuration allows Paytia to:

• Securely capture customer card details using PCI-DSS compliant DTMF suppression

• Prevent card data from ever entering Aircall, agents, recordings, or CRM systems

• Route calls back to Aircall seamlessly once payment capture is complete

Important:
Your Aircall configuration, users, call flows, and integrations remain unchanged.
Paytia simply becomes the upstream carrier for your telephone numbers.

Use Case

This setup is designed for businesses that:

• Use Aircall for inbound and outbound telephony

• Need secure telephone card capture

• Want to remove PCI scope from agents, recordings, and Aircall systems

• Require Paytia to handle payment capture before calls reach Aircall

How the Call Flow Works

1. Customer dials your existing business number

2. Call terminates on Paytia (instead of Aircall)

3. Paytia securely captures card details using the customer’s phone keypad

4. Once complete, Paytia routes the call to Aircall

5. Aircall handles the rest of the call exactly as before

Customer → Paytia (Secure Card Capture) → Aircall → Agent

Important Clarification

• Telephone numbers are ported from Aircall to Paytia

• Numbers are not ported into Aircall

• Paytia becomes the number holder

• Aircall remains your call-handling platform

Step 1 – Raise a Support Ticket with Aircall

You must request the port-out details directly from Aircall.

When raising the ticket:

• Clearly state that you are raising the case to 'port out for SIP trunking via Paytia'

• Confirm the numbers will be ported to Paytia

• Request all required porting information (see below)

Step 2 – Information Required from Aircall

Ask the Aircall support team to provide the following information exactly as listed below.

Required Porting Details

Tip:
Any mismatch between these details and Aircall’s records can delay the port.

Step 3 – Submit Porting Request to Paytia

Once you receive the required information from Aircall:

1. Send the full porting details to Paytia Support

2. Include:

   • All Aircall-provided porting information

   • The list of numbers to be ported

   • Your preferred porting date (if applicable)

Paytia will:

• Validate the information

• Submit the port request to the relevant carrier

• Coordinate porting timelines with you

Step 4 – Configuration and Go-Live

After porting completes:

• Paytia activates secure payment capture on the numbers

• Calls are routed from Paytia to Aircall

• Your existing Aircall:

  • Users

  • IVRs

  • Queues

  • Call routing

  • CRM integrations
    remain unchanged

No changes are required inside Aircall unless you choose to update routing logic.

What Does Not Change

• Aircall login and user access

• Agent workflows

• Call recordings (card data never enters recordings)

• CRM integrations connected to Aircall

• Reporting and analytics in Aircall

Benefits of This Setup

• ✔ Removes card data from Aircall completely

• ✔ Reduces PCI-DSS scope and compliance burden

• ✔ Prevents agents hearing or handling card details

• ✔ Works with existing Aircall deployments

• ✔ No retraining required for agents

Support and Assistance

If you need help with:

• Porting coordination

• Aircall ticket wording

• Payment flow configuration

• Testing before go-live

Contact Paytia Support via the support portal.

So to wrap up

Porting numbers from Aircall to Paytia allows you to keep your Aircall setup exactly as it is while introducing a secure, compliant payment capture layer in front of your calls. Paytia handles sensitive card data, Aircall handles conversations, and your business benefits from improved security with minimal disruption.