This chapter describes the Oracle Communications Services Gatekeeper OneAPI Payment interface standards for RESTful web services.
This section describes the standards compliance for the OneAPI Payment interface standards for RESTful web services.
Services Gatekeeper complies with the RESTful web services RESTful bindings for Parlay X Web Services–Payment specification. See Table 1-1, "Audio Call Specification Compliance Table" for the supported version and a link to its location.
The OneAPI Payment interface complies with the schema definition for the XML data type definitions for OMA RESTful Network API for Payment specification. See Table 1-9, "Payment Communication Service Specifications" for the supported version and a link to its location.
Table 23-1 lists the data structures that Services Gatekeeper supports from the RESTful bindings for Parlay X Web Services–Payment specification.
Table 23-1 OneAPI Payment ParlayREST Data Structure Compliance
API Data Structure | Compliant? | Comments |
---|---|---|
Type: PaymentTransactionList |
Yes |
NA |
Type: AmountTransaction |
Yes |
NA |
Type: AmountSplitTransaction |
Yes |
NA |
Type: VolumeTransaction |
Yes |
NA |
Type: VolumeSplitTransaction |
Yes |
NA |
Type: AmountReservationTransaction |
Yes |
NA |
Type: VolumeReservationTransaction |
Yes |
NA |
Type: PaymentAmount |
Yes |
NA |
Type: ChargingMetaData |
Yes |
NA |
Type: EndUserShare |
Yes |
NA |
Type: Rating Parameter |
Yes |
NA |
Enumeration: TransactionOperationStatus |
Yes |
NA |
Values of the Link "rel" attribute |
Yes |
NA |
Resource: All payment transactions for an end user |
Yes |
NA |
Resource: All amount charge and refund transactions for an end user |
Yes |
NA |
Resource: All amount split charge transactions for an end user |
Yes |
NA |
Resource: Individual amount charge or refund transaction for an end user |
Yes |
NA |
Resource: Individual amount split charge transaction for an end use |
Yes |
NA |
Resource: All volume charge and refund transactions for an end user |
Yes |
NA |
Resource: All volume split charge transactions for an end user |
Yes |
NA |