Changes for page card-transaction

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -26,14 +26,19 @@
26	26
27	27	== Summary ==
28	28
29		-The card transaction api is used for cars payments against accounts. The transaction part handles the integration for cars using card terminology. All transaction ends up on an account. There are two major concepts:
	29	+(% class="box successmessage" %)
	30	+(((
	31	+The card transaction api is used for making card payments against credit-accounts, it uses card terminology. All card transactions ends up on a credit-account that maintains the financial balances.
	32	+)))
30	30
	34	+There are card transactions has two major concepts:
	35	+
31	31	* **Authorizations** which are used to validate if payments can be done, they will end up as reservations on the account without any financial transaction. An authorization will in most cases end up in financial transaction a "Purchase".
32	32	* **Financial transactions** Purchase, Cache-Withdrawals and Reversals. Each financial transaction can be reversed using reversals.
33	33
34		-Authorizations and Authorization/Cancellations are the only real-time transactions that take place instantly on at the point of sale (POS) (eg. cache register or online during payment). Although most transactions follow the authorization > financial transaction flow, there are cases with financial transactions without corresponding authorization. The most typical scenario is when a POS-Terminal loses connection with the internet. To prevent an all-stand-still at the point of sales, the cards usually hold an offline-limit that limits the amount of purchase that can be made unauthorized. (% class="small" %)The offline-limit (if such exist) is regulated in the agreement between the card-issuer and the consumer.
	39	+Authorizations and Authorization/Cancellations are the only real-time transactions, they take place instantly on at the point of sale (POS) (eg. cache register or online payment).
35	35
36		-Financial transactions are batch processed in clearing files and do not occur in real time.
	41	+Although most transactions follow the authorization > financial transaction flow, there are cases with financial transactions without corresponding authorization. The most typical scenario is when a POS-Terminal loses connection with the internet. To prevent an all-stand-still at the point of sales, the cards usually hold an offline-limit that limits the amount of purchase that can be made unauthorized. (% class="small" %)The offline-limit (if such exist) is regulated in the agreement between the card-issuer and the consumer.
37	37
38	38	=== Mapping card-transaction to credit-account ===
39	39
...	...	@@ -55,9 +55,20 @@
55	55	|(% style="width:241px" %)[[../reversals>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HReversals]]|(% style="width:155px" %)(% class="small" %)Financial Transaction|(% style="width:177px" %)(((
56	56	[[../transactions>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HTransactions]] (% class="small" %)##**"type" : "credit"**##
57	57	)))|(% style="width:591px" %)The payer returns the merchandise and the money i returned to the account holders account
58		-|(% style="width:241px" %)[[../reversals/../corrections>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HCorrections]]|(% style="width:155px" %)(% class="small" %)Financial Transaction|(% style="width:177px" %)[[../transactions>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HTransactions]] (% class="small" %)##**"type" : "purchase"**##|(% style="width:591px" %)
	63	+|(% style="width:241px" %)[[../reversals/../corrections>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HCorrections]]|(% style="width:155px" %)(% class="small" %)Financial Transaction|(% style="width:177px" %)[[../transactions>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HTransactions]] (% class="small" %)##**"type" : "purchase"**##|(% style="width:591px" %)A correction of the reversal transaction if it was invalid.
59	59
	65	+(% class="box floatinginfobox" %)
	66	+(((
	67	+Financial transactions of type purchase that do not have a corresponding authorization are usually subject to liability shift, meaning that if the transaction fails in the clearing the financial risk is transferred to the mechants. Financial transactions are batch processed in clearing files and do not occur in real time.
	68	+)))
60	60
	70	+(% class="wikigeneratedid" %)
	71	+== ==
	72	+
	73	+(% class="wikigeneratedid" %)
	74	+== ==
	75	+
	76	+(% class="wikigeneratedid" %)
61	61	== Authorizations ==
62	62
63	63	(% class="wikigeneratedid" %)