Parlay X Payment (PostPaid) allows
you to easily enable an application to charge an amount against a user account
or place money into a user account. The Web service then writes this charging
information to a local database.
Parlay X Payment (PostPaid) is
designed as a simple Parlay X Web services support API to enable billing support
through a Web interface. Using this high-level abstraction Parlay X specification,
developers can quickly create payment applications to interact with Parlay
X Web services APIs though a simple XML-based messaging exchange.
Call flows
The following steps show the general process
flow for this Web service using an offline charging system:
- A Parlay X payment client (an application created to interface with Parlay X Payment (PostPaid))
sends charging (billing) information in a SOAP message over HTTP to Access Gateway.
- Access Gateway inspects
the Web service request and adds policy data retrieved from Subscription Management
to the SOAP message.
- Access Gateway invokes Parlay X Payment (PostPaid).
- Parlay X Payment (PostPaid) invokes Admission Control component Web service to
determine if the system has enough capacity to handle the request. If it does
process continues, if not an error is generated and returned to the payment
client.
- If processing continues, the TWSS Administration Console obtains
the policy data from the SOAP message. If the policy data is missing, the
policy defaults that were set through the TWSS Administration Console.
- If Parlay X Payment (PostPaid) has
Payment Usage Records enabled, payment charging data is sent to Usage Record component Web service, and a record is created in the service usage database.
- If Parlay X Payment (PostPaid) has
CEI enabled, Parlay X Payment (PostPaid) creates
a common base event representing a payment record in the CEI event repository.
- If Parlay X Payment (PostPaid) has
Results Usage Records enabled, payment service results data is sent to Usage Record component Web service,
and a record is created in the service usage database.
- The billing mediator application (an application created to interface
with Parlay X Payment (PostPaid))
pulls the payment record from the service usage database and the CEI event
repository and updates the user account information on the database in the
billing domain.
- The billing mediator application may delete the payment record from the
service usage database and the CEI event repository when the user account
is successfully updated.
- If a fault or alarm condition occurs during the process flow Parlay X Payment (PostPaid) sends error information to Fault and Alarm component Web service,
which creates fault and alarm records (as common base events) in the CEI repository
and outputs alarms to JMX.
Interfaces
- AmountCharging
- chargeAmount
- Charge an amount against a user account.
- refundAmount
- Place money into a user account.
- VolumeCharging
- chargeVolume
- Charge against a user account an amount that has been specified as a volume.
- refundVolume
- Place into a user account money that has been specified as a volume.