From 08d45fa14b3f57ec5ecc72a83d6cbddd46ddc842 Mon Sep 17 00:00:00 2001 From: JamesRamm Date: Fri, 7 Apr 2017 20:32:05 +0100 Subject: [PATCH] Fixes #29 --- docs/usage/payments.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/usage/payments.rst b/docs/usage/payments.rst index d68b747..8703eab 100644 --- a/docs/usage/payments.rst +++ b/docs/usage/payments.rst @@ -53,4 +53,7 @@ To implement your own payment integration, you must implement the payment gatewa You can define your own requirements for the request data to be submitted to the functions. ``create_payment`` is called in a POST request to the ``checkout/`` api. ``get_token`` is similarly called -in a POST request to the ``checkout/token/`` api. \ No newline at end of file +in a POST request to the ``checkout/token/`` api. + +Longclaw aims to be as minimal as possible in order to get the job done. This is why longclaw currently only offers the barest minimum +support necessary to directly create payments with the backend payment provider. \ No newline at end of file