KEYED, SWIPED, EMV, ON_FILE, or CONTACTLESS.
*/
- @JsonIgnore
+ @JsonProperty("entry_method")
public OptionalCVV_ACCEPTED, CVV_REJECTED, or CVV_NOT_CHECKED.
*/
- @JsonIgnore
+ @JsonProperty("cvv_status")
public OptionalAVS_ACCEPTED, AVS_REJECTED, or AVS_NOT_CHECKED.
*/
- @JsonIgnore
+ @JsonProperty("avs_status")
public OptionalPIN, SIGNATURE, PIN_AND_SIGNATURE, ON_DEVICE, or NONE.
*/
- @JsonIgnore
+ @JsonProperty("verification_method")
public OptionalSUCCESS, FAILURE, or UNKNOWN.
*/
- @JsonIgnore
+ @JsonProperty("verification_results")
public OptionalNote: The actual statement description varies and is likely to be truncated and appended with * additional information on a per issuer basis.
*/ - @JsonIgnore + @JsonProperty("statement_description") public Optionaltrue, the card must be present.
*/
- @JsonIgnore
+ @JsonProperty("refund_requires_card_presence")
public OptionalThe credit card's non-confidential details.
*/ @@ -525,17 +394,6 @@ public Builder entryMethod(String entryMethod) { return this; } - public Builder entryMethod(NullableThe status code returned from the Card Verification Value (CVV) check. The code can be
* CVV_ACCEPTED, CVV_REJECTED, or CVV_NOT_CHECKED.
The status code returned from the Address Verification System (AVS) check. The code can be
* AVS_ACCEPTED, AVS_REJECTED, or AVS_NOT_CHECKED.
The status code returned by the card issuer that describes the payment's * authorization status.
@@ -603,17 +439,6 @@ public Builder authResultCode(String authResultCode) { return this; } - public Builder authResultCode(NullableFor EMV payments, the application ID identifies the EMV application used for the payment.
*/ @@ -628,17 +453,6 @@ public Builder applicationIdentifier(String applicationIdentifier) { return this; } - public Builder applicationIdentifier(NullableFor EMV payments, the human-readable name of the EMV application used for the payment.
*/ @@ -653,17 +467,6 @@ public Builder applicationName(String applicationName) { return this; } - public Builder applicationName(NullableFor EMV payments, the cryptogram generated for the payment.
*/ @@ -678,17 +481,6 @@ public Builder applicationCryptogram(String applicationCryptogram) { return this; } - public Builder applicationCryptogram(NullableFor EMV payments, the method used to verify the cardholder's identity. The method can be
* PIN, SIGNATURE, PIN_AND_SIGNATURE, ON_DEVICE, or NONE.
For EMV payments, the results of the cardholder verification. The result can be
* SUCCESS, FAILURE, or UNKNOWN.
The statement description sent to the card networks.
*Note: The actual statement description varies and is likely to be truncated and appended with
@@ -757,17 +527,6 @@ public Builder statementDescription(String statementDescription) {
return this;
}
- public Builder statementDescription(Nullable Deprecated: Use Details about the device that took the payment. Information about errors encountered during the request.Payment.device_details instead.
When the subscription plan of the newly created subscription has a fixed number of cycles and the canceled_date
- * occurs before the subscription plan expires, the specified canceled_date sets the date when the subscription
+ * occurs before the subscription plan completes, the specified canceled_date sets the date when the subscription
* stops through the end of the last cycle.
When the subscription plan of the newly created subscription has a fixed number of cycles and the canceled_date
- * occurs before the subscription plan expires, the specified canceled_date sets the date when the subscription
+ * occurs before the subscription plan completes, the specified canceled_date sets the date when the subscription
* stops through the end of the last cycle.
When the subscription plan of the newly created subscription has a fixed number of cycles and the canceled_date
- * occurs before the subscription plan expires, the specified canceled_date sets the date when the subscription
+ * occurs before the subscription plan completes, the specified canceled_date sets the date when the subscription
* stops through the end of the last cycle.
When the subscription plan of the newly created subscription has a fixed number of cycles and the canceled_date
- * occurs before the subscription plan expires, the specified canceled_date sets the date when the subscription
+ * occurs before the subscription plan completes, the specified canceled_date sets the date when the subscription
* stops through the end of the last cycle.
The device type. * See DeviceType for possible values
*/ - ManufacturerStage type(@NotNull String type); + ManufacturerStage type(@NotNull DeviceAttributesDeviceType type); Builder from(DeviceAttributes other); } @@ -285,7 +285,7 @@ public interface _FinalStage { @JsonIgnoreProperties(ignoreUnknown = true) public static final class Builder implements TypeStage, ManufacturerStage, _FinalStage { - private String type; + private DeviceAttributesDeviceType type; private String manufacturer; @@ -328,7 +328,7 @@ public Builder from(DeviceAttributes other) { */ @java.lang.Override @JsonSetter("type") - public ManufacturerStage type(@NotNull String type) { + public ManufacturerStage type(@NotNull DeviceAttributesDeviceType type) { this.type = Objects.requireNonNull(type, "type must not be null"); return this; } diff --git a/src/main/java/com/squareup/square/types/DeviceAttributesDeviceType.java b/src/main/java/com/squareup/square/types/DeviceAttributesDeviceType.java new file mode 100644 index 00000000..24ccfdba --- /dev/null +++ b/src/main/java/com/squareup/square/types/DeviceAttributesDeviceType.java @@ -0,0 +1,86 @@ +/** + * This file was auto-generated by Fern from our API Definition. + */ +package com.squareup.square.types; + +import com.fasterxml.jackson.annotation.JsonCreator; +import com.fasterxml.jackson.annotation.JsonValue; + +public final class DeviceAttributesDeviceType { + public static final DeviceAttributesDeviceType TERMINAL = + new DeviceAttributesDeviceType(Value.TERMINAL, "TERMINAL"); + + public static final DeviceAttributesDeviceType HANDHELD = + new DeviceAttributesDeviceType(Value.HANDHELD, "HANDHELD"); + + private final Value value; + + private final String string; + + DeviceAttributesDeviceType(Value value, String string) { + this.value = value; + this.string = string; + } + + public Value getEnumValue() { + return value; + } + + @java.lang.Override + @JsonValue + public String toString() { + return this.string; + } + + @java.lang.Override + public boolean equals(Object other) { + return (this == other) + || (other instanceof DeviceAttributesDeviceType + && this.string.equals(((DeviceAttributesDeviceType) other).string)); + } + + @java.lang.Override + public int hashCode() { + return this.string.hashCode(); + } + + publicThe mac address of the device in this network.
+ */ + @JsonSetter(value = "mac_address", nulls = Nulls.SKIP) + public Builder macAddress(OptionalValue of measure.
+ */ @JsonSetter(value = "value", nulls = Nulls.SKIP) public Builder value(OptionalThe mac address of the device in this network.
+ */ + @JsonSetter(value = "mac_address", nulls = Nulls.SKIP) + public Builder macAddress(OptionalSee Category for possible values
+ *Category of the device status. + * See Category for possible values
*/ @JsonSetter(value = "category", nulls = Nulls.SKIP) public Builder category(OptionalIf this field is not set in a CreateLoyaltyAccount request, Square populates it after the buyer's first action on their account
- * (when AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service in Square Point of Sale.
This field is typically specified in a CreateLoyaltyAccount request when creating a loyalty account for a buyer who already interacted with their account.
- * For example, you would set this field when migrating accounts from an external system. The timestamp in the request can represent a current or previous date and time, but it cannot be set for the future.
AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service on Square Point of Sale.
+ * If this field is set in a CreateLoyaltyAccount request, it is meant to be used when there is a loyalty migration from another system and into Square.
+ * In that case, the timestamp can reflect when the buyer originally enrolled in the previous system. It may represent a current or past date, but cannot be set in the future.
+ * Note: Setting this field in this scenario does not, by itself, impact the first-party enrollment flow on Square Point of Sale.
The timestamp when the buyer joined the loyalty program, in RFC 3339 format. This field is used to display the Enrolled On or Member Since date in first-party Square products.
*If this field is not set in a CreateLoyaltyAccount request, Square populates it after the buyer's first action on their account
- * (when AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service in Square Point of Sale.
This field is typically specified in a CreateLoyaltyAccount request when creating a loyalty account for a buyer who already interacted with their account.
- * For example, you would set this field when migrating accounts from an external system. The timestamp in the request can represent a current or previous date and time, but it cannot be set for the future.
AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service on Square Point of Sale.
+ * If this field is set in a CreateLoyaltyAccount request, it is meant to be used when there is a loyalty migration from another system and into Square.
+ * In that case, the timestamp can reflect when the buyer originally enrolled in the previous system. It may represent a current or past date, but cannot be set in the future.
+ * Note: Setting this field in this scenario does not, by itself, impact the first-party enrollment flow on Square Point of Sale.
The timestamp when the buyer joined the loyalty program, in RFC 3339 format. This field is used to display the Enrolled On or Member Since date in first-party Square products.
*If this field is not set in a CreateLoyaltyAccount request, Square populates it after the buyer's first action on their account
- * (when AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service in Square Point of Sale.
This field is typically specified in a CreateLoyaltyAccount request when creating a loyalty account for a buyer who already interacted with their account.
- * For example, you would set this field when migrating accounts from an external system. The timestamp in the request can represent a current or previous date and time, but it cannot be set for the future.
AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service on Square Point of Sale.
+ * If this field is set in a CreateLoyaltyAccount request, it is meant to be used when there is a loyalty migration from another system and into Square.
+ * In that case, the timestamp can reflect when the buyer originally enrolled in the previous system. It may represent a current or past date, but cannot be set in the future.
+ * Note: Setting this field in this scenario does not, by itself, impact the first-party enrollment flow on Square Point of Sale.
The timestamp when the buyer joined the loyalty program, in RFC 3339 format. This field is used to display the Enrolled On or Member Since date in first-party Square products.
*If this field is not set in a CreateLoyaltyAccount request, Square populates it after the buyer's first action on their account
- * (when AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service in Square Point of Sale.
This field is typically specified in a CreateLoyaltyAccount request when creating a loyalty account for a buyer who already interacted with their account.
- * For example, you would set this field when migrating accounts from an external system. The timestamp in the request can represent a current or previous date and time, but it cannot be set for the future.
AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service on Square Point of Sale.
+ * If this field is set in a CreateLoyaltyAccount request, it is meant to be used when there is a loyalty migration from another system and into Square.
+ * In that case, the timestamp can reflect when the buyer originally enrolled in the previous system. It may represent a current or past date, but cannot be set in the future.
+ * Note: Setting this field in this scenario does not, by itself, impact the first-party enrollment flow on Square Point of Sale.
The timestamp when the buyer joined the loyalty program, in RFC 3339 format. This field is used to display the Enrolled On or Member Since date in first-party Square products.
*If this field is not set in a CreateLoyaltyAccount request, Square populates it after the buyer's first action on their account
- * (when AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service in Square Point of Sale.
This field is typically specified in a CreateLoyaltyAccount request when creating a loyalty account for a buyer who already interacted with their account.
- * For example, you would set this field when migrating accounts from an external system. The timestamp in the request can represent a current or previous date and time, but it cannot be set for the future.
AccumulateLoyaltyPoints or CreateLoyaltyReward is called). In first-party flows, Square populates the field when the buyer agrees to the terms of service on Square Point of Sale.
+ * If this field is set in a CreateLoyaltyAccount request, it is meant to be used when there is a loyalty migration from another system and into Square.
+ * In that case, the timestamp can reflect when the buyer originally enrolled in the previous system. It may represent a current or past date, but cannot be set in the future.
+ * Note: Setting this field in this scenario does not, by itself, impact the first-party enrollment flow on Square Point of Sale.
Tips for external vendors such as a 3rd party delivery courier must be recorded using Order.service_charges.
*This amount is specified in the smallest denomination of the applicable currency (for example, * US dollar amounts are specified in cents). For more information, see * Working with Monetary Amounts.
@@ -977,7 +978,8 @@ public Builder amountMoney(Money amountMoney) { } /** - *The amount designated as a tip.
+ *The amount designated as a tip for the seller's staff.
+ *Tips for external vendors such as a 3rd party delivery courier must be recorded using Order.service_charges.
*This amount is specified in the smallest denomination of the applicable currency (for example, * US dollar amounts are specified in cents). For more information, see * Working with Monetary Amounts.
diff --git a/src/main/java/com/squareup/square/types/Subscription.java b/src/main/java/com/squareup/square/types/Subscription.java index 9a9ad2e4..a7068d72 100644 --- a/src/main/java/com/squareup/square/types/Subscription.java +++ b/src/main/java/com/squareup/square/types/Subscription.java @@ -62,6 +62,8 @@ public final class Subscription { private final OptionalYYYY-MM-DD-formatted date when the subscription enters a terminal state.
+ */
+ @JsonIgnore
+ public OptionalThe YYYY-MM-DD-formatted date when the subscription enters a terminal state.