Paytia SIP services

Before any calls can be routed through Paytia’s secure payment platform, the following SIP-trunking prerequisites must be met. All IP addresses, DNS entries, ports and telephone numbers listed must be mutually trusted and configured on both sides of the integration.

Paytia services are firewall protected so you will need to provide IP addresses for internet facing (WAN) interfaces that will send calls to Paytia.

1. Carrier → Paytia (Inbound Calls)

1. Inbound Call Routing
   • Your carrier must route incoming DDI/DDI ranges to Paytia’s SIP endpoint at 52.51.166.39 or tel.pay729.net.

2. Trust Configuration

   • Paytia’s public IP address 52.51.166.39 (or DNS tel.pay729.net) must be added to your carrier’s “trusted peers” list.

   • Your carrier’s SIP signalling IP(s) must be defined as trusted on Paytia’s platform.

3. Numbering

   • All telephone numbers/DDIs that the carrier will pass to Paytia must be registered in Paytia as “trusted numbers” (to avoid unauthorised call injection).

2. Paytia → Carrier (Outbound Calls)

1. Outbound Routing
   • Paytia must be able to send outbound SIP INVITEs to your carrier’s SIP gateway from 52.51.166.39 (or tel.pay729.net).

2. Trust Configuration

   • Your carrier must trust Paytia’s sending IP 52.51.166.39 (or DNS tel.pay729.net) for SIP signalling.

   • Paytia must trust your carrier’s SIP signalling IP(s) on its egress ACL.

3. Authentication (if required)

   • If your carrier requires SIP registration or digest authentication, Paytia will be provided with a SIP username/password.

4. Numbering

   • Any CLI/DDI that Paytia will send “from” must already be configured in Paytia as a valid outbound number.

3. Paytia → Your PABX (Inbound Calls)

1. Inbound Call Routing
   • Calls entering Paytia from the carrier, once de-scoped of card data, must be forwarded via SIP to your PABX.

2. Trust Configuration

   • Your PABX’s WAN IP address (or SIP/FQDN) must be defined as a trusted peer in Paytia.

   • Paytia’s SIP sending IP 52.51.166.39 (or DNS tel.pay729.net) must be trusted by your PABX and bound to the SIP-trunk profile.

3. Numbering

   • All DDIs that you wish Paytia to forward into your PABX must be present in Paytia’s “trusted numbers” list.

4. Your PABX → Paytia (Outbound Calls)

1. Outbound Routing
   • Calls from your users that require payment must be routed from your PABX to Paytia’s SIP gateway at 52.51.166.39 (or tel.pay729.net).

2. PABX Configuration

   • SIP-Trunk Profile: Create a trunk for Paytia, pointing at 52.51.166.39 (or tel.pay729.net).

   • Dial-Plan Rules: Ensure the outbound dialling pattern (e.g. 9+DDI) routes via the Paytia trunk.

3. Trust Configuration

   • Your PABX must trust Paytia’s signalling IP 52.51.166.39 (or DNS tel.pay729.net) on that trunk.

   • Paytia must also trust your PABX’s WAN IP(s) to accept inbound SIP from the PBX.

4. Numbering

   • Any “Calling Number” presented by your PABX that Paytia will process must be pre-registered as a trusted number in Paytia.

Additional Notes

• Account Provisioning
  A live Paytia account must exist before any SIP credentials or trunk settings can be issued.

• Contact techsupport@paytia.com for SIP profile creation.

• Security and Compliance
  All SIP signalling should use TLS where supported. Paytia will handle PCI-scope reduction on every call by capturing and removing card data before forwarding.

• Network Ports
  Ensure the following ports are open bidirectionally between your network and Paytia’s endpoint:

  • UDP 5060 for standard SIP signalling

  • TCP 5061 for SIP over TLS

• Paytia Endpoint Details

  • IP Address: 52.51.166.39

  • DNS Name: tel.pay729.net

• Support
  To request SIP credentials or report configuration issues, please raise a ticket with techsupport@paytia.com.

Once all of the above trust relationships, IP/DNS entries, port-openings and telephone-number mappings are in place, end-to-end call routing (customer ↔ carrier ↔ Paytia ↔ your PABX) will function seamlessly, with cardholder data always handled securely.