Calling Card Validation a. BellSouth is authorized to validate a 14-digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth.
Calling Card Validation. 9.2.8.11.1 SBC-AMERITECH shall permit CLEC to access SBC- AMERITECH’s LIDB to validate calling card numbers and requests for xxxx-to-third party or collect billing. SBC-AMERITECH shall provide LIDB access in a non-discriminatory manner by a SS7 formatted data query to determine the validity of the billing method requested by the caller.
Calling Card Validation refers to the activity of determining whether a particular calling card number exists as stated or otherwise provided by a caller.
Calling Card Validation. If Access One chooses to offer Tel Line Number TLN and/or Special Billing Number (SBN credit cards, calling card validation will be supported for Access One customer data in the LIDB.
Calling Card Validation. Fraud Control
Calling Card Validation. If Satcom chooses to offer Tel Line Number TLN and/or Special Billing Number (SBN credit cards, calling card validation will be supported for Satcom customer data in the LIDB.
Calling Card Validation. If Supra Telecommunications and Information Systems, Inc. chooses to offer Tel Line Number TLN and/or Special Billing Number (SBN credit cards, calling card validation will be supported for Supra Telecommunications and Information Systems, Inc. customer data in the LIDB.
Calling Card Validation. If DIECA chooses to offer Tel Line Number TLN and/or Special Billing Number (SBN credit cards, calling card validation will be supported for DIECA customer data in the LIDB.
Calling Card Validation. AT&T is authorized to validate a 14-Digit calling card number where the first 10 digits are a line number or special billing number assigned by AT&T, and where the last four digits (PIN) are a security code assigned by AT&T.
Calling Card Validation. BA shall process MCIm's subscriber records in LIDB at least at parity with BA subscriber records, with respect to other LIDB functions.
