summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMarcin Gębala <maarcin.gebala@gmail.com>2014-09-10 17:26:26 +0200
committerMarcin Gębala <maarcin.gebala@gmail.com>2014-09-10 17:26:26 +0200
commit8862064ff28cb82508cdbf83d0590a64b4a042bb (patch)
tree901944a682d3a9edf3dd0f55e06c06ebed02acf3 /doc
parent20ab3819e48ecdba2377e392b7cecb317929dc49 (diff)
downloaddjango-payments-taler-8862064ff28cb82508cdbf83d0590a64b4a042bb.tar.gz
django-payments-taler-8862064ff28cb82508cdbf83d0590a64b4a042bb.tar.bz2
django-payments-taler-8862064ff28cb82508cdbf83d0590a64b4a042bb.zip
Move fraud status section to different chapter
Diffstat (limited to 'doc')
-rw-r--r--doc/modules.rst18
-rw-r--r--doc/usage.rst33
2 files changed, 26 insertions, 25 deletions
diff --git a/doc/modules.rst b/doc/modules.rst
index a8caf8c..eff33e8 100644
--- a/doc/modules.rst
+++ b/doc/modules.rst
@@ -90,24 +90,6 @@ Cybersource allows you to pass Merchant-Defined Data, which is additional inform
>>> payment.attrs.merchant_defined_data = {'01': 'foo', '02': 'bar'}
-Fraud statuses
-""""""""""""""
-
-Cybersource provides services used for fraud detection. When using this gateway, you can check the fraud status of your payment by accessing ``payment.fraud_status`` and ``payment.fraud_message`` fields. The possible fraud statuses are:
-
-``unknown``
- The fraud status is unknown. This is the default status for other gateways, that do not involve fraud detection.
-
-``accept``
- Fraud was not detected.
-
-``reject``
- Fraud service detected some problems with the payment. Inspect the details by accessing the ``payment.fraud_message`` field.
-
-``review``
- The payment was marked for review.
-
-
Dotpay
------
diff --git a/doc/usage.rst b/doc/usage.rst
index 3fa8ea0..6be5c89 100644
--- a/doc/usage.rst
+++ b/doc/usage.rst
@@ -27,6 +27,17 @@ Making a payment
#. Redirect the user to your payment handling view.
+Payment amounts
+---------------
+The :class:`Payment` instance provides two fields that let you check the total charged amount and the amount actually captured::
+
+ >>> payment.total
+ Decimal('181.38')
+
+ >>> payment.captured_amount
+ Decimal('0')
+
+
Payment statuses
----------------
A payment may have one of several statuses, that indicates its current state. The status is stored in ``status`` field of your :class:`Payment` instance. Possible statuses are:
@@ -53,12 +64,20 @@ A payment may have one of several statuses, that indicates its current state. Th
An error occurred during the communication with the payment gateway. Inspect the contents of the ``payment.message`` and ``payment.extra_data`` fields to see the gateway response.
-Payment amounts
----------------
-The :class:`Payment` instance provides two fields that let you check the total charged amount and the amount actually captured::
- >>> payment.total
- Decimal('181.38')
+Fraud statuses
+--------------
- >>> payment.captured_amount
- Decimal('0')
+Some gateways provide services used for fraud detection. You can check the fraud status of your payment by accessing ``payment.fraud_status`` and ``payment.fraud_message`` fields. The possible fraud statuses are:
+
+``unknown``
+ The fraud status is unknown. This is the default status for gateways, that do not involve fraud detection.
+
+``accept``
+ Fraud was not detected.
+
+``reject``
+ Fraud service detected some problems with the payment. Inspect the details by accessing the ``payment.fraud_message`` field.
+
+``review``
+ The payment was marked for review.