payment_cases
2016-09-26 01:17:23 0 举报
payment_cases是一个涵盖了各种支付场景的案例集合。这些案例包括了在线购物、银行转账、信用卡支付、移动支付等多种支付方式,以及它们在不同行业和领域的应用。通过学习这些案例,我们可以了解到不同支付方式的优缺点,以及如何根据实际需求选择合适的支付方式。此外,payment_cases还关注支付安全和风险管理,为我们提供了防范欺诈和保护客户资金的有效方法。总之,payment_cases是一个全面而实用的支付知识库,无论您是支付行业的从业者还是普通用户,都能从中受益匪浅。
作者其他创作
大纲/内容
maintenance service (involving materials)
success ?
Payment
(automatic) process card payment
planned serviceplanned delivery of goods
card
UnexpectedIntervention
Bill
payment
PaymentReduction
(postponed)wired
Cancelled
product delivery (option: installation)
identify the right process phase (based on date/time in SMS and date/time period of planned intervention)
this is what the client agreed about to receive during planned interventionthis is what billed advances will be based on
select any costs relating to the type of payment (these costs are defined via UI in back-end with products & services)
product sales
costs can apply depending on payment type
multiple interventions may be needed to be planned to cover the expected performance (in some cases where things don't go as expected) - extra charges may or may not be applied
PaymentTypes
to be added:the options for the user to speak/send a command to the system to block an invoice from being sent automatically because payment is incomplete (user can finalise the details later e.g. back in the office - being pushed also by the software not to forget it)
ExtraPayment
can client pay?is client willing to pay ?
CardPaymentTypes
this is what the client is billed for and paying for (after the planned intervention has taken place or as an advance to it)
RealisedPayment
Unplanned
ExpectedPayment
define 2 payments for the same service each 50% by default
cash payment exception: no adapted change so a difference remains (+ or -)
yes
no payment (now)
payment failed
payment registered
repair service
multiple services can be covered by 1 intervention
ExpectedIntervention
reduction can be :- ristorno- correction for excessive payment on previous service- correction as a compensation for low(er) quality of service
payments ?
in the case of exceptional interventions collaborator may want to create in 1 move : dossier/phase-extra intervention-expected payment + actual payment covering 100% of the intervention
(manual) register payment
warn collaborator in question and put a flag for that SMS to be assigned to a new dossier/phase yet to be created by the user
actual intervention
service
PlannedIntervention
Intervention
no
detection / analysis / advice service
warn collaborator in question and put a flag for that service/expected payment to be cleared only when the user confirmed the 50/50% division of payment
+1 sms for same period (and bankcard device/collaborator)
planned meeting found but linked to another collaborator than deduced from the SMS
cash
no planned meeting can be found at all
interventie (Dutch)intervention (French)
ResourcePlanning
PriceOffer
exceptions ?
RealisedIntervention
ReversedPayment
price / cost
type ?
0 条评论
下一页