Transaction Storage Service
- Balaji Varadharajan
Component basics
Title | |
Description | The transaction storage service has a very similar objective as that of file storage service. It stores the individual transaction information that is received in its original form as a CLOB object along with the Zeus Transaction Control Number that is created for the transaction. The raw transaction information stored by this service can be retrieved by other services for any purpose that they see fit their needs, but the data within this service should not be updated as it is the true reflection of the transaction data that was received. This data is typically used by the outbound services where the marketplace that send these transaction request for a response with the data as it was sent by them with few additional details. The outbound service will typically call this to get the original transaction as it was received make the necessary updates and send it back to the marketplace.
|
Anatomy diagram |
|
Key to anatomy diagram |
Specifications
Usage |
|
|---|---|
Variations |
|
Behavior |
|
Style |
Additional guidance
Content | |
|---|---|
Accessibility | |
Mobile | |
Best practices | |
Related |