square_api_client/models/enums/
invoice_request_method.rs

1//! Model for InvoiceRequestMethod enum.
2
3/// Specifies the action for Square to take for processing the invoice.
4///
5/// For example, email the invoice, charge a customer's card on file, or do nothing. DEPRECATED at
6/// version 2021-01-21. The corresponding `request_method` field is replaced by the
7/// `Invoice.delivery_method` and `InvoicePaymentRequest.automatic_payment_source` fields.
8use serde::{Deserialize, Serialize};
9#[derive(Clone, Debug, Deserialize, Eq, PartialEq, Serialize)]
10#[serde(rename_all = "SCREAMING_SNAKE_CASE")]
11pub enum InvoiceRequestMethod {
12    /// Directs Square to send invoices, reminders, and receipts to the customer using email. Square
13    /// sends the invoice after it is published (either immediately or at the `scheduled_at time`,
14    /// if specified in the [Invoice]).
15    #[deprecated]
16    Email,
17    /// Directs Square to charge the card on file on the `due_date` specified in the payment request
18    /// and to use email to send invoices, reminders, and receipts.
19    #[deprecated]
20    ChargeCardOnFile,
21    /// Directs Square to take no specific action on the invoice. In this case, the seller (or the
22    /// application developer) follows up with the customer for payment. For example, a seller might
23    /// collect a payment in the Seller Dashboard or use the Point of Sale (POS) application. The
24    /// seller might also share the URL of the Square-hosted invoice page (`public_url`) with the
25    /// customer requesting payment.
26    #[deprecated]
27    ShareManually,
28    /// Directs Square to charge the bank account on file on the `due_date` specified in the payment
29    /// request and to use email to send invoices, reminders, and receipts.
30    ///
31    /// The bank on file payment method applies only to recurring invoices that sellers create in
32    /// the Seller Dashboard or other Square first-party applications. The bank account is provided
33    /// by the customer during the payment flow. You cannot set `CHARGE_BANK_ON_FILE` as a request
34    /// method using the Invoices API.
35    #[deprecated]
36    ChargeBankOnFile,
37    /// Directs Square to send invoices and receipts to the customer using SMS (text message).
38    /// Square sends the invoice after it is published (either immediately or at the `scheduled_at`
39    /// time, if specified in the [Invoice]).
40    ///
41    /// You cannot set `SMS` as a request method using the Invoices API.
42    #[deprecated]
43    Sms,
44    /// Directs Square to charge the card on file on the `due_date` specified in the payment request
45    /// and to use SMS (text message) to send invoices and receipts.
46    ///
47    /// You cannot set `SMS_CHARGE_CARD_ON_FILE` as a request method using the Invoices API.
48    #[deprecated]
49    SmsChargeCardOnFile,
50    /// Directs Square to charge the bank account on file on the `due_date` specified in the payment
51    /// request and to use SMS (text message) to send invoices and receipts.
52    ///
53    /// The bank on file payment method applies only to recurring invoices that sellers create in
54    /// the Seller Dashboard or other Square first-party applications. The bank account is provided
55    /// by the customer during the payment flow. You cannot set `SMS_CHARGE_BANK_ON_FILE` as a
56    /// request method using the Invoices API.
57    #[deprecated]
58    SmsChargeBankOnFile,
59}