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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,38 @@
1
1
# Change Log
2
2
3
+
## Version 9.1.0.20210317 (2021-03-17)
4
+
5
+
## Existing API updates
6
+
7
+
***Payments API:**
8
+
*[CreatePayment](https://developer.squareup.com/reference/square_2021-03-17/payments-api/create-payment). Until now, the `CreatePayment` endpoint supported only taking card payments. In this release, the API now supports cash and external payments. For more information, see [Take Payments.](https://developer.squareup.com/docs/payments-api/take-payments)
9
+
*[UpdatePayment](https://developer.squareup.com/reference/square_2021-03-17/payments-api/update-payment). This new endpoint enables developers to change the payment amount and tip amount after a payment is created. For more information, see [Update Payments.](https://developer.squareup.com/docs/payments-api/update-payments)
10
+
11
+
***Invoices API:**
12
+
*[InvoiceDeliveryMethod](https://developer.squareup.com/reference/square_2021-03-17/enums/InvoiceDeliveryMethod) enum. Added the read-only `SMS` value.
13
+
*[InvoiceRequestMethod](https://developer.squareup.com/reference/square_2021-03-17/enums/InvoiceRequestMethod) enum (deprecated). Added the read-only `SMS`, `SMS_CHARGE_CARD_ON_FILE`, and `SMS_CHARGE_BANK_ON_FILE` values for backward compatibility.
14
+
15
+
These values direct Square to send invoices and receipts to customers using SMS (text message). SMS settings can be configured from first-party Square applications only; they cannot be configured from the Invoices API. Square does not send invoice reminders when using SMS to communicate with customers.
16
+
17
+
18
+
***Terminal API:**
19
+
*[TerminalCheckout](https://developer.squareup.com/reference/square_2021-03-17/objects/TerminalCheckout). Previously, `TerminalCheckout` only supported tapped, dipped, or swiped credit cards. It now supports manual card entry and e-money. Added the `payment_type` field to denote a request for a manually entered payment card or an e-money payment.
20
+
*[TerminalCheckoutPaymentType.](https://developer.squareup.com/reference/square_2021-03-17enums/TerminalCheckoutPaymentType) A new enum for the Terminal checkout payment types that can be requested.
21
+
*[E-money support](https://developer.squareup.com/docs/terminal-api/e-money-payments) is now available for Terminal checkout requests in Japan.
22
+
23
+
24
+
## SDKs
25
+
***Square Java SDK:**
26
+
* Updated the OkHttp dependency to version 4.9.0.
27
+
* Fixed a `NullPointerException` when passing an empty order ID to the `UpdateOrder` method.
28
+
29
+
## Documentation updates
30
+
31
+
***Multi-language code examples.** Previously, various topics showed only cURL examples for the REST API operations. These topics now show examples in multiple languages. You can use the language drop-down list to choose a language.
32
+
33
+
*[When to Use Connect V1.](https://developer.squareup.com/docs/build-basics/using-connect-v1) Content is revised to reflect the most current information about when to use the Connect V1 API.
represented by customer's card on file or a card nonce). In addition
84
-
to the payment source, the request must include the
85
-
amount to accept for the payment.
83
+
Creates a payment using the provided source. You can use this endpoint
84
+
to charge a card (credit/debit card or
85
+
Square gift card) or record a payment that the seller received outside of Square
86
+
(cash payment from a buyer or a payment that an external entity
87
+
procesed on behalf of the seller).
86
88
87
-
There are several optional parameters that you can include in the request
88
-
(for example, tip money, whether to autocomplete the payment, or a reference ID
89
-
to correlate this payment with another system).
90
-
91
-
The `PAYMENTS_WRITE_ADDITIONAL_RECIPIENTS` OAuth permission is required
92
-
to enable application fees.
89
+
The endpoint creates a
90
+
`Payment` object and returns it in the response.
93
91
94
92
```python
95
93
defcreate_payment(self,
@@ -215,10 +213,59 @@ elif result.is_error():
215
213
```
216
214
217
215
216
+
# Update Payment
217
+
218
+
Updates a payment with the APPROVED status.
219
+
You can update the `amount_money` and `tip_money` using this endpoint.
220
+
221
+
```python
222
+
defupdate_payment(self,
223
+
payment_id,
224
+
body)
225
+
```
226
+
227
+
## Parameters
228
+
229
+
| Parameter | Type | Tags | Description |
230
+
| --- | --- | --- | --- |
231
+
|`payment_id`|`string`| Template, Required | The ID of the payment to update. |
232
+
|`body`|[`Update Payment Request`](/doc/models/update-payment-request.md)| Body, Required | An object containing the fields to POST for the request.<br><br>See the corresponding object definition for field details. |
0 commit comments