Check customer billing support

JSON API v3

POST /api/v3/projects/{projectId}/billing/check

Checks whether the given customer (MSISDN) is supported for activation and tariffication within the specified project.

v4 signature payload: {customerPayload} (e.g. {msisdn} for mobile phone)

Request parameters

Field	Type	Required	Description
`projectId`	integer (int32)	yes

Request body

Field	Type	Required	Description
`msisdn`	string	—	Customer MSISDN in international E.164 format (no `+`)

Request example


{
  "msisdn": "79600000000"
}

Response example


{
  "success": true,
  "data": {
    "supported": true,
    "customer": {
      "type": "mobile_phone",
      "msisdn": "79600000000"
    }
  }
}

Response codes

Code	Description
`200`	Billing support result
`400`	Validation or business request error
`401`	Authentication failed (missing/invalid signature or timestamp)
`403`	Project access denied or IP not whitelisted
`422`	Business validation error
`500`	Unexpected platform error
`503`	Service temporarily unavailable

XML API v2.9

POST /API/XML/InvoiceManagementService.ashx

Checks whether billing is supported for the given customer. XML request type: <CheckCustomerBillingSupportRequest>.

This method allows to check the ability of request activation and further tariffication for a particular client with MSISDN within a particular project.

HTTP Headers:

Callisto-Protocol-Version: 2
SignatureVersion: 3

Request parameters

Field	Type	Required	Description
`Callisto-Protocol-Version`	`2`	yes	Protocol version
`SignatureVersion`	integer (int32, default `1`)	—	Signature version number

Request body

Field	Type	Required	Description
`CheckCustomerBillingSupportRequest`	object	yes	The customer is a polymorphic element: exactly one of `MobilePhoneCustomer`, `BankCardCustomer`, `UndefinedBankCardCustomer` (the element name defines the subtype). There is no `CustomerInfo` wrapper in the request.
`CheckCustomerBillingSupportRequest.ProjectID`	integer (int32)	yes	Project ID in the Platform system. Assigned during project setup.
`CheckCustomerBillingSupportRequest.UndefinedMobilePhoneCustomer`	object	—	Platform customer type. The sandbox does not support it — use `MobilePhoneCustomer`.
`CheckCustomerBillingSupportRequest.UndefinedMobilePhoneCustomer.NetworkID`	integer (int32)	yes
`CheckCustomerBillingSupportRequest.UndefinedMobilePhoneCustomer.Email`	string	—
`CheckCustomerBillingSupportRequest.MobilePhoneCustomer`	object	—	Customer identification by mobile phone number. MSISDN is the primary identifier.
`CheckCustomerBillingSupportRequest.MobilePhoneCustomer.MSISDN`	string	yes	Client’s MSISDN (Mobile Subscriber Integrated Services Digital Number) in international format without ’+’ sign
`CheckCustomerBillingSupportRequest.MobilePhoneCustomer.Email`	string (email)	—	Client’s e-mail address
`CheckCustomerBillingSupportRequest.BankCardCustomer`	object	—	Customer identification by bank card. Used for card payment scenarios.
`CheckCustomerBillingSupportRequest.BankCardCustomer.Email`	string (email)	—	Client’s e-mail address
`CheckCustomerBillingSupportRequest.BankCardCustomer.Source`	string	yes	Source Name in Merchant’s system (unique for Partner Service). Should be a unique identifier (e.g. resource/brand name) guaranteeing global uniqueness for parameters source+MerchantCustomerId in all systems.
`CheckCustomerBillingSupportRequest.BankCardCustomer.Country`	string	yes	Country code (ISO 3166-1 alpha-2, lowercase)
`CheckCustomerBillingSupportRequest.BankCardCustomer.MerchantCustomerId`	string	yes	Customer ID in Merchant’s system (unique)
`CheckCustomerBillingSupportRequest.UndefinedBankCardCustomer`	object	—	Bank card customer identification without full data set. Used for initial card payment when card details are not yet known.
`CheckCustomerBillingSupportRequest.UndefinedBankCardCustomer.Source`	string	—	Source Name in Merchant’s system (unique for Partner Service). Should guarantee global uniqueness for parameters source+MerchantCustomerId.
`CheckCustomerBillingSupportRequest.UndefinedBankCardCustomer.Country`	string	yes	Country code (ISO 3166-1 alpha-2, lowercase)
`CheckCustomerBillingSupportRequest.UndefinedBankCardCustomer.MerchantCustomerId`	string	yes	Customer ID in Merchant’s system (unique)
`CheckCustomerBillingSupportRequest.UndefinedBankCardCustomer.Email`	string (email)	—	Client’s e-mail address
`CheckCustomerBillingSupportRequest.UndefinedCustomer`	object	—	Platform customer type. The sandbox does not support it — use `MobilePhoneCustomer`, `BankCardCustomer` or `UndefinedBankCardCustomer`.
`CheckCustomerBillingSupportRequest.UndefinedCustomer.Country`	string	—
`CheckCustomerBillingSupportRequest.UndefinedCustomer.Email`	string	—
`Header`	object	yes	Request header with authentication. Included in every API request.
`Header.Authentication`	object	yes	Request authentication data. All three fields are mandatory for every request.
`Header.Authentication.Login`	string	yes	Merchant Login assigned by the Platform
`Header.Authentication.NowUtc`	string	yes	Current UTC time in yyyyMMddHHmmss format. Must not differ from platform system time by more than 20 minutes.
`Header.Authentication.Signature`	string	yes	HMAC request signature. Calculated as: LOWERCASE(HMACSHA256(Password, Login + LOWERCASE(HMACSHA256(Password, NowUtc))))
`Header.RequestAttempt`	integer (int32)	—	Ordinal invoice request number (for idempotency). Starting from 0.
`Header.Gateway`	object	—	Platform service block in the request header. The sandbox does not read it: the block is ignored and affects neither the signature nor processing.
`Header.Gateway.Signature`	string	—
`Header.Gateway.ContractInfo`	object	—
`Header.Gateway.ContractInfo.DesiredExpirationTimeUtc`	string (date-time)	—

Request example


<?xml version="1.0" encoding="utf-8"?>
<Request>
  <Header>
    <Authentication>
      <Login>demo_login</Login>
      <NowUtc>20260921120000</NowUtc>
      <Signature>0000000000000000000000000000000000000000000000000000000000000000</Signature>
      <SignatureVersion>3</SignatureVersion>
    </Authentication>
  </Header>
  <CheckCustomerBillingSupportRequest>
          <ProjectID>1001</ProjectID>
          <ClientIP>127.0.0.1</ClientIP>
          <MobilePhoneCustomer>
            <MSISDN>79600000000</MSISDN>
          </MobilePhoneCustomer>
        </CheckCustomerBillingSupportRequest>
</Request>

Response example


<?xml version="1.0" encoding="utf-8"?>
<Response>
  <CheckCustomerBillingSupportResponse>
    <MobilePhoneCustomer>
      <MSISDN>79600000000</MSISDN>
      <Country>ru</Country>
      <NetworkID>7</NetworkID>
      <OperatorID>22</OperatorID>
    </MobilePhoneCustomer>
    <IsCustomerBillingSupported>true</IsCustomerBillingSupported>
  </CheckCustomerBillingSupportResponse>
  <ResultCode>0</ResultCode>
  <ResultDescription>OK</ResultDescription>
</Response>