You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- You may not refund more than the available amount
16
+
- You may create multiple refunds for one payment, as long as sufficient refundable amount remains
9
17
10
-
Basic load information about payment refund,
18
+
## Loading Refund Information
11
19
12
-
after client call can be rendered information about refund how you like,
13
-
or refund form can be rendered if some amount for refund is available.
20
+
You can load the refund information for a payment and render it however you prefer—either as details for the user or to display a refund form when a refund is possible.
Copy file name to clipboardExpand all lines: doc/saving-authorization.md
+19-16Lines changed: 19 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,45 +1,48 @@
1
-
# Saving card authorization
1
+
# Saving Card Authorization
2
2
3
-
It is possible to remember customer card information by using the save_authorization parameter upon payment creation.This allow easier and seamless payment creation, through following child payments, without additional customer card authorization.It shoud however NOT be confused with (and used for) [subscription payments](subscription.md).
3
+
It is possible to store a customer’s card authorization by enabling the `save_authorization` parameter when creating a payment.
4
+
This allows you to create follow-up (“child”) payments seamlessly, without requiring the customer to reauthorize their card.
4
5
5
-
## Creating payment with save_authorization flag
6
+
However, this feature must not be confused with — or used for — [subscription payments](subscription.md). Those have a separate workflow and rules.
Copy file name to clipboardExpand all lines: doc/subscription.md
+43-38Lines changed: 43 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,57 +1,63 @@
1
-
# Subscription payments
1
+
# Subscription Payments
2
2
3
-
It is possible to create long term subscription for your customers. The setup for subsription is done through regular endpoint for payment creation, but with the subscription properties set. The payment created can then be repeatedly paid by the customer, through a different endpoint.
3
+
Subscription payments allow you to charge a customer repeatedly over time.
4
+
A subscription is initialized through a standard payment creation request, but with subscription properties attached.
5
+
Once the initial (parent) payment is completed, follow-up (child) payments can be realized using dedicated subscription endpoints.
4
6
5
-
There are three different use cases with different endpoints for subscription payments, depending on payment time and payment amount needs.
6
-
* Fixed time interval & fixed payment amount
7
-
* Variable time interval & fixed payment amount
8
-
* Fixed time interval & variable payment amount
7
+
There are three main subscription types, depending on whether the time interval and payment amount are fixed or variable:
8
+
- Fixed time interval & fixed amount
9
+
- Variable time interval & fixed amount
10
+
- Fixed time interval & variable amount
9
11
10
-
The time interval or amount with fixed value is always set in the first (parent) payment upon payment creation. It is your responsibility to adhere to the values set in the parent payment. If you need to change the fixed payment amount or time period, a new subscription payment with different parameters must be used.
12
+
Any value marked as fixed must be set in the parent payment, and it is your responsibility to adhere to it when creating child payments.
13
+
If your subscription requires a different amount or interval, you must create a new parent subscription payment.
11
14
12
-
**RECURRING PAYMENTS MUST BE ENABLED ON PROJECT**
15
+
⚠️ **Important / Prerequisites**
16
+
-**Recurring payments must be enabled on your project**.
13
17
14
-
## Creating payment with subscription properties
18
+
19
+
## Creating a Payment with Subscription Properties
0 commit comments