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
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,19 @@
1
1
# Change Log
2
2
3
+
## Version 6.4.0.20200923 (2020-09-23)
4
+
## Existing API updates
5
+
* Invoices API (beta)
6
+
*[InvoiceStatus](https://developer.squareup.com/reference/square_2020-09-23/enums/InvoiceStatus) enum. Added the `PAYMENT_PENDING` value. Previously, the Invoices API returned a `PAID` or `PARTIALLY_PAID` status for invoices in a payment pending state. Now, the Invoices API returns a `PAYMENT_PENDING` status for all invoices in a payment pending state, including those previously returned as `PAID` or `PARTIALLY_PAID`.
7
+
* Payments API
8
+
*[ListPayment](https://developer.squareup.com/reference/square_2020-09-23/payments-api/list-payments). The endpoint now supports the `limit` parameter.
9
+
* Refunds API
10
+
*[ListPaymentRefunds](https://developer.squareup.com/reference/square_2020-09-23/refunds-api/list-payment-refunds). The endpoint now supports the `limit` parameter.
11
+
*[DeviceDetails](https://developer.squareup.com/reference/square_2020-09-23/objects/DeviceDetails#definition__property-device_installation_id). The object now includes the `device_installation_id` field.
12
+
## Documentation updates
13
+
*[Payment status.](https://developer.squareup.com/docs/payments-api/take-payments#payment-status) Added details about the `Payment.status` changes and how the status relates to the seller receiving the funds.
14
+
*[Refund status.](https://developer.squareup.com/docs/payments-api/refund-payments#refund-status) Added details about the `PaymentRefund.status` changes and how the status relates to the cardholder receiving the funds.
15
+
*[CreateRefund errors.](https://developer.squareup.com/docs/payments-api/error-codes#createrefund-errors) Added documentation for the `REFUND_DECLINED` error code.
16
+
3
17
## Version 6.3.0.20200826 (2020-08-26)
4
18
## Existing API updates
5
19
* Orders API
@@ -254,4 +268,4 @@ All SDKs have been updated to support the following changes:
254
268
*__Beta release:__ SDKs updated to support the new [CashDrawerShifts](cashdrawershift-api/reporting) API.
255
269
256
270
* Square now follows the semantic versioning scheme for all SDKs except PHP and Node.js. This versioning scheme uses three numbers to delineate MAJOR, MINOR, and PATCH versions of our SDK. In addition, the SDK version also includes the API version so you know what Square API version the SDK is related to. For more information, see [Versioning and SDKs](build-basics/versioning-overview#versioning-and-sdks).
257
-
* Java, .Net, Python, and Ruby SDKs are now version 4.0.0. Java and .Net SDKs have breaking changes in version 4.0.0. Ruby and Python do not have breaking changes.
271
+
* Java, .Net, Python, and Ruby SDKs are now version 4.0.0. Java and .Net SDKs have breaking changes in version 4.0.0. Ruby and Python do not have breaking changes.
Square debits the disputed amount from the seller’s Square
101
103
account. If the Square account balance does not have
102
104
sufficient funds, Square debits the associated bank account.
103
-
For an overview of the Disputes API, see [Overview](https://developer.squareup.com/docs/docs/disputes-api/overview).
105
+
106
+
Accept a dispute: [https://developer.squareup.com/docs/disputes-api/process-disputes#accept-a-dispute](https://developer.squareup.com/docs/disputes-api/process-disputes#accept-a-dispute)
Uploads a file to use as evidence in a dispute challenge. The endpoint accepts
246
249
HTTP multipart/form-data file uploads in HEIC, HEIF, JPEG, PDF, PNG,
247
250
and TIFF formats.
248
-
For more information, see [Challenge a Dispute](https://developer.squareup.com/docs/docs/disputes-api/process-disputes#challenge-a-dispute).
251
+
252
+
Challenge a dispute: [https://developer.squareup.com/docs/disputes-api/process-disputes#challenge-a-dispute](https://developer.squareup.com/docs/disputes-api/process-disputes#challenge-a-dispute)
Uploads text to use as evidence for a dispute challenge. For more information, see
291
-
[Challenge a Dispute](https://developer.squareup.com/docs/docs/disputes-api/process-disputes#challenge-a-dispute).
294
+
Uploads text to use as evidence for a dispute challenge.
295
+
296
+
Challenge a dispute: [https://developer.squareup.com/docs/disputes-api/process-disputes#challenge-a-dispute](https://developer.squareup.com/docs/disputes-api/process-disputes#challenge-a-dispute)
and evidence automatically provided by Square, when
337
-
available. For more information, see
338
-
[Challenge a Dispute](https://developer.squareup.com/docs/docs/disputes-api/process-disputes#challenge-a-dispute).
342
+
available.
343
+
344
+
Challenge a dispute: [https://developer.squareup.com/docs/disputes-api/process-disputes#challenge-a-dispute](https://developer.squareup.com/docs/disputes-api/process-disputes#challenge-a-dispute)
Returns a list of invoices for a given location. The response
25
25
is paginated. If truncated, the response includes a `cursor` that you
26
26
use in a subsequent request to fetch the next set of invoices.
27
-
For more information about retrieving invoices, see [Retrieve invoices](https://developer.squareup.com/docs/docs/invoices-api/overview#retrieve-invoices).
27
+
28
+
Retrieve an invoice: [https://developer.squareup.com/docs/invoices-api/overview#retrieve-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#retrieve-an-invoice)
@@ -66,8 +67,9 @@ Creates a draft [invoice](#type-invoice)
66
67
for an order created using the Orders API.
67
68
68
69
A draft invoice remains in your account and no action is taken.
69
-
You must publish the invoice before Square can process it (send it to the customer's email address or charge the customer’s card on file).
70
-
For more information, see [Manage Invoices Using the Invoices API](https://developer.squareup.com/docs/docs/invoices-api/overview).
70
+
You must publish the invoice before Square can process it (send it to the customer's email address or charge the customer’s card on file).
71
+
72
+
Create and publish an invoice: [https://developer.squareup.com/docs/invoices-api/overview#create-and-publish-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#create-and-publish-an-invoice)
@@ -162,8 +164,9 @@ retrieve invoices. In the current implementation, you can only specify one locat
162
164
optionally one customer.
163
165
164
166
The response is paginated. If truncated, the response includes a `cursor`
165
-
that you use in a subsequent request to fetch the next set of invoices.
166
-
For more information about retrieving invoices, see [Retrieve invoices](https://developer.squareup.com/docs/docs/invoices-api/overview#retrieve-invoices).
167
+
that you use in a subsequent request to fetch the next set of invoices.
168
+
169
+
Retrieve an invoice: [https://developer.squareup.com/docs/invoices-api/overview#retrieve-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#retrieve-an-invoice)
Deletes the specified invoice. When an invoice is deleted, the
219
222
associated Order status changes to CANCELED. You can only delete a draft
220
223
invoice (you cannot delete an invoice scheduled for publication, or a
221
-
published invoice).
224
+
published invoice).
225
+
226
+
Delete an invoice: [https://developer.squareup.com/docs/invoices-api/overview#delete-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#delete-an-invoice)
Retrieve an invoice: [https://developer.squareup.com/docs/invoices-api/overview#retrieve-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#retrieve-an-invoice)
Updates an invoice by modifying field values, clearing field values, or both
289
296
as specified in the request.
290
297
There are no restrictions to updating an invoice in a draft state.
291
-
However, there are guidelines for updating a published invoice.
292
-
For more information, see [Update an invoice](https://developer.squareup.com/docs/docs/invoices-api/overview#update-an-invoice).
298
+
However, there are guidelines for updating a published invoice.
299
+
300
+
Update an invoice: [https://developer.squareup.com/docs/invoices-api/overview#update-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#update-an-invoice)
Cancels an invoice. The seller cannot collect payments for
372
380
the canceled invoice.
373
381
374
-
You cannot cancel an invoice in a terminal state: `PAID`, `REFUNDED`, `CANCELED`, or `FAILED`.
382
+
You cannot cancel an invoice in a terminal state: `PAID`, `REFUNDED`, `CANCELED`, or `FAILED`.
383
+
384
+
Cancel an invoice: [https://developer.squareup.com/docs/invoices-api/overview#cancel-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#cancel-an-invoice)
@@ -420,8 +430,7 @@ based on the invoice configuration. For example, the status changes to `UNPAID`
420
430
Square emails the invoice or `PARTIALLY_PAID` if Square charge a card on file for a portion of the
421
431
invoice amount).
422
432
423
-
For more information, see
424
-
[Create and publish an invoice](https://developer.squareup.com/docs/docs/invoices-api/overview#create-and-publish-an-invoice).
433
+
Create and publish an invoice: [https://developer.squareup.com/docs/invoices-api/overview#create-and-publish-an-invoice](https://developer.squareup.com/docs/invoices-api/overview#create-and-publish-an-invoice)
Copy file name to clipboardExpand all lines: doc/models/create-payment-request.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ For information about application fees in a payment, see
19
19
| Name | Type | Tags | Description | Getter |
20
20
| --- | --- | --- | --- | --- |
21
21
|`SourceId`|`String`|| The ID for the source of funds for this payment. This can be a nonce<br>generated by the Payment Form or a card on file made with the Customers API. | String getSourceId() |
22
-
|`IdempotencyKey`|`String`|| A unique string that identifies this CreatePayment request. Keys can be any valid string<br>but must be unique for every CreatePayment request.<br><br>Max: 45 characters<br><br>See [Idempotency keys](https://developer.squareup.com/docs/basics/api101/idempotency) for more information. | String getIdempotencyKey() |
22
+
|`IdempotencyKey`|`String`|| A unique string that identifies this CreatePayment request. Keys can be any valid string<br>but must be unique for every CreatePayment request.<br><br>Max: 45 characters<br><br>Note: The number of allowed characters might be less than the stated maximum, if multi-byte<br>characters are used.<br><br>See [Idempotency keys](https://developer.squareup.com/docs/basics/api101/idempotency) for more information. | String getIdempotencyKey() |
23
23
|`AmountMoney`|[`Money`](/doc/models/money.md)|| Represents an amount of money. `Money` fields can be signed or unsigned.<br>Fields that do not explicitly define whether they are signed or unsigned are<br>considered unsigned and can only hold positive amounts. For signed fields, the<br>sign of the value indicates the purpose of the money transfer. See<br>[Working with Monetary Amounts](https://developer.squareup.com/docs/build-basics/working-with-monetary-amounts)<br>for more information. | Money getAmountMoney() |
24
24
|`TipMoney`|[`Money`](/doc/models/money.md)| Optional | Represents an amount of money. `Money` fields can be signed or unsigned.<br>Fields that do not explicitly define whether they are signed or unsigned are<br>considered unsigned and can only hold positive amounts. For signed fields, the<br>sign of the value indicates the purpose of the money transfer. See<br>[Working with Monetary Amounts](https://developer.squareup.com/docs/build-basics/working-with-monetary-amounts)<br>for more information. | Money getTipMoney() |
25
25
|`AppFeeMoney`|[`Money`](/doc/models/money.md)| Optional | Represents an amount of money. `Money` fields can be signed or unsigned.<br>Fields that do not explicitly define whether they are signed or unsigned are<br>considered unsigned and can only hold positive amounts. For signed fields, the<br>sign of the value indicates the purpose of the money transfer. See<br>[Working with Monetary Amounts](https://developer.squareup.com/docs/build-basics/working-with-monetary-amounts)<br>for more information. | Money getAppFeeMoney() |
Copy file name to clipboardExpand all lines: doc/models/invoice-status.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,14 @@ Indicates the status of an invoice.
10
10
11
11
| Name | Description |
12
12
| --- | --- |
13
-
|`DRAFT`| The invoice is a draft. You must publish a draft invoice before Square can process it.<br>A draft invoice has no public_url, so it is not available to customers. |
13
+
|`DRAFT`| The invoice is a draft. You must publish a draft invoice before Square can process it.<br>A draft invoice has no `public_url`, so it is not available to customers. |
14
14
|`UNPAID`| The invoice is published but not yet paid. |
15
-
|`SCHEDULED`| The invoice is scheduled to be processed. On scheduled date,<br>Square emails the invoice (if the `request_method` is EMAIL),<br>charge the customer's card (if `request_method` is CHARGE_CARD_ON_FILE),<br>or take no action (if the `request_method` is SHARE_MANUALLY).<br>The invoice status then changes accordingly (`UNPAID`, `PAID`, or `PARTIALLY_PAID`). |
15
+
|`SCHEDULED`| The invoice is scheduled to be processed. On the scheduled date,<br>Square emails the invoice (if the `request_method` is `EMAIL`),<br>charges the customer's card (if the `request_method` is `CHARGE_CARD_ON_FILE`),<br>or takes no action (if the `request_method` is `SHARE_MANUALLY`).<br>The invoice status then changes accordingly (`UNPAID`, `PAID`, or `PARTIALLY_PAID`). |
16
16
|`PARTIALLY_PAID`| A partial payment is received for the invoice. |
17
17
|`PAID`| The customer paid the invoice in full. |
18
18
|`PARTIALLY_REFUNDED`| The invoice is paid (or partially paid) and some but not all the amount paid is<br>refunded. |
19
19
|`REFUNDED`| The full amount that the customer paid for the invoice is refunded. |
20
20
|`CANCELED`| The invoice is canceled. Square no longer requests payments from the customer.<br>The `public_url` page remains and is accessible, but it displays the invoice<br>as cancelled and does not accept payment. |
21
21
|`FAILED`| Square canceled the invoice due to suspicious activity. |
22
+
|`PAYMENT_PENDING`| A payment on the invoice was initiated but has not yet been processed. <br><br>When in this state, invoices cannot be updated and other payments cannot be initiated. |
Copy file name to clipboardExpand all lines: doc/models/list-payment-refunds-request.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ Max results per page: 100
19
19
|`LocationId`|`String`| Optional | Limit results to the location supplied. By default, results are returned<br>for all locations associated with the merchant. | String getLocationId() |
20
20
|`Status`|`String`| Optional | If provided, only refunds with the given status are returned.<br>For a list of refund status values, see [PaymentRefund](#type-paymentrefund).<br><br>Default: If omitted refunds are returned regardless of status. | String getStatus() |
21
21
|`SourceType`|`String`| Optional | If provided, only refunds with the given source type are returned.<br>- `CARD` - List refunds only for payments where card was specified as payment<br>source.<br><br>Default: If omitted refunds are returned regardless of source type. | String getSourceType() |
22
+
|`Limit`|`Integer`| Optional | Maximum number of results to be returned in a single page.<br>It is possible to receive fewer results than the specified limit on a given page.<br><br>If the supplied value is greater than 100, at most 100 results will be returned.<br><br>Default: `100`| Integer getLimit() |
0 commit comments