| Party Payment ABE UML Documentation |
Common Domain::Party Payment ABE
Association PartyPaymentReceivedFrom
A PartyPayment represents the transfer of wealth from one Party to another. So it is received from a PartyRole and made to a PartyRole.The PartyPayment might be either inbound or outbound and always uses a PaymentMethod.A PartyPayment might specify the BankAccount to which the payment is transferred.The diagram below shows different types of PaymentMethods identified at the present time, currently allowed for paying due amounts such as CheckPM, DigitalWalletPM, LoyaltyBurnPM...As all the PaymentMethod might not be yet described as a sub-class of PaymentMethod, a PaymentMethod might be described a PaymentMethodSpecification defining the characteristics.ThirdPartyCollectionPM is an example of payment method, using which payment can be made through the third party, such as bank transfer, payment tool(like PayPal, Alipay).A PaymentMethod is owned by a PartyRole.A PaymentPlan may specify PaymentMethods to use for auto-pay. If several PaymentMethod are specified, a priority is given to each of them. Over time, PartyPayments are collected according to the PaymentPlan.
Properties:
Alias | |
Is Abstract | false |
Is Derived | false |
Is Leaf | false |
Keywords | |
Kind | 0 - simple |
Name | PartyPaymentReceivedFrom |
Name Expression | |
Namespace | «013» Party Payment ABE |
Owned Template Signature | |
Owner | «013» Party Payment ABE |
Owning Template Parameter | |
Package | «013» Party Payment ABE |
Qualified Name | SID Models::Common Domain::Party Payment ABE::PartyPaymentReceivedFrom |
Representation | |
Stereotype | |
Template Parameter | |
Visibility | Public |
| Party Payment ABE UML Documentation |