Secure phone payments for 3CX

Paytia sits beside 3CX as a SIP trunk you import via a pre-built XML profile, so there's no rebuild of your dial plan or PBX config. Once it's in, agents trigger a secure capture session by dialling 729 mid-call and the customer keys their card on their own handset.

Yes. The keypad tones the customer enters are masked before they reach 3CX, so your call recording captures the conversation but never the card number. That means you can keep continuous recording running for QA and dispute handling without having to pause-and-resume around payments.

It works the same way across all 3CX deployment types — hosted by 3CX, on your own server, or in a private cloud. The SIP trunk profile is identical and Paytia doesn't need any inbound access to your 3CX server.

Almost nothing. The agent stays in the 3CX softphone or desk phone they already use, dials 729 to start the capture, and watches a Paytia browser tab for live status — card BIN, masked PAN, authorisation result. They never leave the call and never type card details into 3CX.

Yes, agents can be assigned payment types they are authorised to use. A simple dropdown menu choice swaps between payment types including immediate capture, card capture to file, Stripe subscription plans, or reserving money on customer cards.

Yes. We work with 3CX resellers who want to bundle secure phone payments alongside the PBX they're already deploying. Each end customer gets their own Paytia account and SIP trunk, billed monthly with no setup fees or contract — so resellers can land it on a per-site basis without committing the customer to anything long-term.