Knowledge Base/General Telephony

Paytia US Number porting

Number Porting (LNP) – Field Explanations Paytia has to carry out the movement of your numbers from your current calls and lines provider to their own service provider. This will allow your calls to be routed directly into Paytia reducing the cost of ...

Number Porting (LNP) – Field Explanations

Paytia has to carry out the movement of your numbers from your current calls and lines provider to their own service provider. This will allow your calls to be routed directly into Paytia reducing the cost of call forwarding and allowing card data to be removed prior to it reaching your telephony services.


This document explains each field required by Paytia when porting (moving) US telephone numbers from an existing service provider. All information must exactly match the records held by the current (losing) carrier to avoid port rejections.


Required Porting Fields Explained

Field Name

Plain-English Explanation

Auth Name*

The full name of the person authorised to approve the number port. This must match the authorised contact on the existing carrier account.

Auth Date*

The date on which the authorised person approved the port request. This confirms when consent was given.

Account Number with current lines provider*

The account number assigned by the current (losing) carrier. This must match exactly what appears on their billing records.

Account PIN/Password

A security PIN or password set on the existing account. Some carriers require this to prevent unauthorised ports. If no PIN exists, this may be left blank or marked N/A.

Billing Telephone Number (BTN/ATN)*

The primary telephone number associated with the account for billing purposes. This identifies the account and is often not the same number being ported.

End User Name*

The legal name of the business or individual that owns the telephone numbers. This must exactly match the name on the current carrier’s records.

Type Of Service*

Indicates whether the service is Business or Residential. This determines which porting rules apply.

Business

Confirms that the numbers belong to a business entity rather than a residential customer.

Service Address

The physical address on file with the current carrier for the phone numbers. This must match their records exactly.

Street Number*

The building or property number of the service address (for example, 12, 100, 42A).

Street Pre-Direction

Any directional prefix that appears before the street name (for example, N, S, E, W, NE).

Street Name*

The actual name of the street (for example, Main, Market, Broadway).

Street Type

The type of street, such as Street, Road, Avenue, Boulevard, Drive, Lane, etc.

Street Post Direction

Any directional suffix that appears after the street name (for example, NW, SE).

Location Type 1

An additional address qualifier, such as Suite, Unit, Floor, Building, or Apartment.

Location Value 1

The specific value for the location type, such as Suite 200, Floor 3, Unit B.

City*

The city associated with the service address on the current carrier’s records.

State*

The US state where the service address is located, typically shown as a two-letter abbreviation (for example, CA, NY, TX).

Zip/Post Code*

The ZIP / Postal code associated with the service address. This must match exactly what the current carrier has on file.


Important Porting Notes

  • Exact data matching is critical
    Any mismatch between the submitted information and the losing carrier’s records can result in a port rejection.


  • BTN is often the primary validation field
    Many US carriers use the Billing Telephone Number as the main account identifier during validation.


  • Service address matters
    The service address on file is typically used for validation, not the billing or mailing address.


  • Authorisation is mandatory
    Ports cannot proceed without clear authorisation from the account holder or authorised contact.


Summary

Providing accurate, carrier-matching information for all required fields significantly reduces delays and rejections during the Inteliquent number porting process.


More in General Telephony

Can I use Agent Capture Assist with my mobile?

Using Agent Capture Assist with Your Mobile Yes, you can use Paytia's Agent Capture Assist with your mobile phone. The service is designed to deliver calls to both landline and mobile numbers, ensuring flexibility for your business needs. Steps to ...

Do I Need to Replace My Existing Telephone Number?

Do I Need to Replace My Existing Telephone Number? No, you do not need to replace your existing telephone number to use Agent Capture Assist. Instead, you can forward calls from your Agent Capture Assist number to your existing business telephone ...

How can I set the telephone number that appears on my customer's phone when you call them?

How to Set the Telephone Number Displayed on Your Customer's Phone Paytia allows you to control what telephone number appears on your customer's phone when you make an outgoing call. You can either present your secure payment number provided by ...

How do I enter my call forwarding number?

How to Enter Your Phone Number as a Call Forwarding Number Follow these steps to set up your call forwarding number in Agent Capture Assist: Step 1: Enter Your Inbound Call Number Log in to your Agent Capture Assist portal using your administrator ...

How do I present calls from a custom telephone number through Paytia?

Presenting Calls from a Custom Telephone Number Through Paytia Overview If your business needs to display a custom telephone number on outbound calls, Paytia offers a solution through the Bespoke CLI (Custom Line Identification) license. This license ...

How do I purchase and deploy multiple Paytia numbers?

If you want to enable payments on multiple customer lines, you can purchase additional Paytia numbers and route them to different destinations in your organization. This article explains how. Why you may require multiple Paytia numbers Paytia ...

Still need help?

Our support team is here to help. Submit a ticket and we'll get back to you within one business day.

Submit a TicketBack to Knowledge Base