Previous
Contents
DocHome
Index
Next
|
| iPlanet Trustbase Payment Services 2.0 Beta Systems Administration Guide |
Chapter 5 Email Notification
Introduction
This document describes the parties that are emailed as notifications of events occurring in the Payment system.
It also describes where the system obtains the email addresses of these parties, which is dependent on the type of messages being sent, i.e. Asynchronous acknowledgements, condition status update notifications, etc.
Signing Certificate
The email address is obtained from the signing certificate(s) of the payment instruction messages. The SubjectAltName extension in these certificates contains the email address.
These addresses are used when asynchronous acknowledgements are sent. Both the Buyer and Seller can receive email notifications of these type of acknowledgements:
email address in TooledUp seller certificate used for signing payment instruction messages
User Database
Buyer information is added to the User database in order to control access to the Condition Management web site. One of the attributes that can be added to the Buyer information profile is an email address.
It is this email address that is used to notify the Buyer of updates to the status of Conditions, and Condition sets. The following acronyms are used:
email address in Buyer details in User Db
Message Contents
For conditional payment instruction messages the email address supplied in the contact element contained within the individual condition elements is used to inform the CDP of updates to the status of conditions relating to the them.
CDP details obtained from the payment instruction message contents
Message Types
All the messages described below relate to SFIM messages, but the results broadly relate to the same as
Payment Order
A Payment Order instruction has been sent to the BFI, via the SFI from the seller, and has been successfully acknowledged with a synchronous Service acknowledgement.
The following acknowledgements have all been sent from the BFI's back end systems, in the following order: PayInst, PaymentExecution, and Payment Completion.
A Payment Completion acknowledgement has been sent from the SFI's back end systems.
Originating From SFI
Payment Completion Ack
Buyer
Yes
1 Buyer Smart Card used for signing
Seller
Yes
Payment Obligation
A Payment Obligation instruction has been sent to the BFI, via the SFI from the seller, and has been successfully acknowledged with a synchronous Service acknowledgement.
The following acknowledgements have all been sent from the BFI's back end systems, in the following order: Obligation, PaymentExecution, and Payment Completion.
A Payment Completion acknowledgement has been sent from the SFI's back end systems.
Originating From SFI
Pay Comp Ack
Buyer
Yes
1 Buyer Smart Card used for signing
Seller
Yes
Conditional Payment Order
A Conditional Payment Order instruction has been sent to the BFI, via the SFI from the seller, and has been successfully acknowledged with a synchronous Service acknowledgement.
This message contains a single condition.
Scenario A
First, a PayInst acknowledgement is sent from the BFI's back end systems.
The CDP then accepts the condition at the BFI's Condition Management web site, which changes the condition status to CDPProcessing.
The CDP then Discharges the condition through the BFI's Condition Management web site, which changes the condition status to Discharged.
The following acknowledgements are then sent from the BFI's back end systems, in the following order: PaymentExecution, and Payment Completion.
A Payment Completion acknowledgement has been sent from the SFI's back end systems.
Originating From SFI
Pay Comp Ack
Buyer
Yes
1 Buyer Smart Card used for signing
Seller
Yes
Scenario B
First, a PayInst acknowledgement is sent from the BFI's back end systems.
The CDP then accepts the condition at the BFI's Condition Management web site, which changes the condition status to CDPProcessing.
When the condition's waive-by-date has passed, a Payment Condition message is sent by iTPS signifying that the condition status has changed to Expired.
Scenario C
First, a PayInst acknowledgement is sent from the BFI's back end systems.
The CDP then accepts the condition at the BFI's Condition Management web site, which changes the condition status to CDPProcessing.
The CDP then fails the condition at the BFI's Condition Management web site, which changes the condition status to failed.
The Buyer then waives the condition at the BFI's Condition Management web site.
The BFI's back end systems acknowledge that the Buyer has the appropriate authority, and a Payment Condition Received Acknowledgement is sent.
This positive acknowledgement updates the condition status to waived.
A Payment Completion acknowledgement has been sent from the SFI's back end systems.
Originating From SFI
Pay Comp Ack
Buyer
Yes
1 Buyer Smart Card used for signing
Seller
Yes
Scenario D
First, a PayInst acknowledgement is sent from the BFI's back end systems.
The CDP accepts the condition for processing then discharges the condition, then the payment is canceled.
The CDP then Discharges the condition through the BFI's Condition Management web site, which changes the condition status to Discharged.
A Payment Cancellation message is then received by the BFI, which successfully returns a synchronous Service acknowledgement.
A Cancellation acknowledgement is then sent from the BFI's back end systems.
Scenario E
First, a PayInst acknowledgement is sent from the BFI's back end systems.
The CDP accepts the condition for processing then discharges the condition, then the payment is canceled.
A Payment Cancellation message is then received by the BFI, which successfully returns a synchronous Service acknowledgement.
A Cancellation acknowledgement is then sent from the BFI's back end systems.
The condition status is now updated to the status Cancelled.
Previous Contents DocHome Index Next
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.
Last Updated October 22, 2002