PayStar API Documentation
  1. API DOC | EN
  • MERCHANT
    • PRODUCTS | EN
    • ПРОДУКТЫ | RU
    • Untitled Doc
    • FEATURES | EN
      • Deposits & Payouts
      • Issues (Tickets)
      • Secure data (One-time secret)
      • Summary Report
      • Payment Analytics
      • Payment Form Analytics
      • Unified audit log
      • Export reports
      • Black list
      • Routing & Cascading
      • Limits
      • Commissions
      • Team
      • My Account
      • PayStar in 100 Questions
    • ВОЗМОЖНОСТИ | RU
      • Депозиты и выплаты
      • Issues (Задачи)
      • Защищённые данные (One-time secret)
      • Сводный отчёт
      • Аналитика по платежам
      • Единый журнал событий
      • Аналитика платёжной формы
      • Экспорт отчётов
      • Черный список
      • Мавршрутизация и Каскады
      • Лимиты
      • Комиссии
      • Команда
      • Мой аккаунт
      • PayStar в 100 вопросах
    • API DOC | EN
      • Introduction
      • Glossary
      • Authorization key
      • Sandbox
      • Additional fields
      • Currencies
      • Bank names
      • Telecom operators
      • Callbacks
      • Error descriptions
      • Tech FAQ
      • Events
      • Payment history v2
      • Integratins
        • Stripe
        • Inwizo
        • 2Checkout
        • Adyen
        • AffiniPay
        • Alikassa
        • AlliancePay
        • Amazon Pay
        • AnyMoney
        • AstroPay
        • Aureavia
        • AurisMyChanger
        • Authorize.Net
        • Avatarix
      • Balance H2H
        GET
      • Deposit H2H - Card & P2P
        POST
      • Deposit H2H - Token
        POST
      • Deposit H2C - Card
        POST
      • Deposit status H2H - PayStar ID
        GET
      • Deposit status H2H - Merch ID
        GET
      • Payout H2H
        POST
      • Payout status H2H - PayStar ID
        GET
      • Payout status H2H - Merch ID
        GET
  • AGENT (REFERRAL)
  1. API DOC | EN

Telecom operators

INFO
The telecom operator name is typically used for routing payments. If the telecom operator is not specified in the request, it will be automatically determined based on the phone number.
However, phone-based detection is often inaccurate and may not be available in certain regions.
We strongly recommend including this field in your requests — doing so will improve payment success rates and enhance the reliability of financial flows.

How to use telecomOperator example#

telecomOperator is used in the additionalFields for deposit and payout. Here's an example of a query using telecomOperator:
curl --request POST \
 --url https://baseurl.com/api/v1/integration/deposit-order \
 --header 'Authorization: Bearer YOUR TOKEN' \
 --header 'Content-Type: application/json' \
 --header 'accept: text/plain' \
 --data '{
  "amount": 100
  "currency": "USD"
  "additionalFields": [
    {
      "key": "phone"
      "value": "+331234567890"
    },
    {
      "key": "telecomOperator"
      "value": "vadafone-uk"
    }
  ]
}'

telecomOperator dictionary#

United Kingdom#

EnumName
vodafone-ukVodafone
o2-ukO2 (Telefónica)
everything-everywhere-ukEverything Everywhere (EE)
talk-talk-ukTalkTalk

Ukraine#

EnumName
kievstar-uaKievstar
vodafon-uaVodafon Ukraine
lifecell-uaLifecell
intertelecom-uaIntertelecom

Republic of Moldova#

EnumName
orange-mdOrange Moldova
moldcell-mdMoldcell
unite-mdUnite

Poland#

EnumName
tMobile-pltMobile Poland
orange-plOrange Poland
play-plPlay
plus-plPlus
lykamobile-plLykamobile
virginMobile-plVirgin

Hungary#

EnumName
magyarTelekom-huMagyar Telekom
telenor-huTelenor
vodafone-huVodafone Hungary

Slovakia#

EnumName
t-com-skT-Com
t-mobile-skT-Mobile
orange-skOrange Slovensko
upc-skUPC

Russia#

EnumName
beeline-ruBeeline
megafon-ruMegafon
mts-ruМТС
rostelecom-ruRostelecom
tele2-ruTele2
yota-ruYota
tmobile-ruTinkoff Mobile
Previous
Bank names
Next
Callbacks
Built with