Package com.stripe.model.treasury

Class Transaction.FlowDetails

java.lang.Object
com.stripe.model.StripeObject
com.stripe.model.treasury.Transaction.FlowDetails
All Implemented Interfaces:
StripeObjectInterface
Enclosing class:
Transaction
public static class Transaction.FlowDetails extends StripeObject
For more details about FlowDetails, please refer to the API Reference.

  • Constructor Details

    • FlowDetails

      public FlowDetails()

  • Method Details

    • getCreditReversal

      public CreditReversal getCreditReversal()
      Legacy CreditReversals are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Received Credits instead of building a new v1 integration.

      You can reverse some ReceivedCredits depending on their network and source flow. Reversing a ReceivedCredit leads to the creation of a new object known as a CreditReversal.

    • getDebitReversal

      public DebitReversal getDebitReversal()
      Legacy DebitReversals are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2.

      You can reverse some ReceivedDebits depending on their network and source flow. Reversing a ReceivedDebit leads to the creation of a new object known as a DebitReversal.

    • getInboundTransfer

      public InboundTransfer getInboundTransfer()
      Legacy InboundTransfers are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Inbound Transfers instead of building a new v1 integration.

      Use InboundTransfers to add funds to your FinancialAccount via a PaymentMethod that is owned by you. The funds will be transferred via an ACH debit.

      Related guide: Moving money with Treasury using InboundTransfer objects

    • getIssuingAuthorization

      public Authorization getIssuingAuthorization()
      When an issued card is used to make a purchase, an Issuing Authorization object is created. Authorizations must be approved for the purchase to be completed successfully.

      Related guide: Issued card authorizations

    • getOutboundPayment

      public OutboundPayment getOutboundPayment()
      Legacy OutboundPayments are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Outbound Payments instead of building a new v1 integration.

      Use OutboundPayments to send funds to another party's external bank account or FinancialAccount. To send money to an account belonging to the same user, use an OutboundTransfer.

      Simulate OutboundPayment state changes with the /v1/test_helpers/treasury/outbound_payments endpoints. These methods can only be called on test mode objects.

      Related guide: Moving money with Treasury using OutboundPayment objects

    • getOutboundTransfer

      public OutboundTransfer getOutboundTransfer()
      Legacy OutboundTransfers are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Outbound Transfers instead of building a new v1 integration.

      Use OutboundTransfers to transfer funds from a FinancialAccount to a PaymentMethod belonging to the same entity. To send funds to a different party, use OutboundPayments instead. You can send funds over ACH rails or through a domestic wire transfer to a user's own external bank account.

      Simulate OutboundTransfer state changes with the /v1/test_helpers/treasury/outbound_transfers endpoints. These methods can only be called on test mode objects.

      Related guide: Moving money with Treasury using OutboundTransfer objects

    • getReceivedCredit

      public ReceivedCredit getReceivedCredit()
      Legacy ReceivedCredits are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Received Credits instead of building a new v1 integration.

      ReceivedCredits represent funds sent to a FinancialAccount (for example, via ACH or wire). These money movements are not initiated from the FinancialAccount.

    • getReceivedDebit

      public ReceivedDebit getReceivedDebit()
      Legacy ReceivedDebits are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Received Debits instead of building a new v1 integration.

      ReceivedDebits represent funds pulled from a FinancialAccount. These are not initiated from the FinancialAccount.

    • getType

      public String getType()
      Type of the flow that created the Transaction. Set to the same value as flow_type.

      One of credit_reversal, debit_reversal, inbound_transfer, issuing_authorization, other, outbound_payment, outbound_transfer, received_credit, or received_debit.

    • setCreditReversal

      public void setCreditReversal(CreditReversal creditReversal)
      Legacy CreditReversals are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Received Credits instead of building a new v1 integration.

      You can reverse some ReceivedCredits depending on their network and source flow. Reversing a ReceivedCredit leads to the creation of a new object known as a CreditReversal.

    • setDebitReversal

      public void setDebitReversal(DebitReversal debitReversal)
      Legacy DebitReversals are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2.

      You can reverse some ReceivedDebits depending on their network and source flow. Reversing a ReceivedDebit leads to the creation of a new object known as a DebitReversal.

    • setInboundTransfer

      public void setInboundTransfer(InboundTransfer inboundTransfer)
      Legacy InboundTransfers are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Inbound Transfers instead of building a new v1 integration.

      Use InboundTransfers to add funds to your FinancialAccount via a PaymentMethod that is owned by you. The funds will be transferred via an ACH debit.

      Related guide: Moving money with Treasury using InboundTransfer objects

    • setIssuingAuthorization

      public void setIssuingAuthorization(Authorization issuingAuthorization)
      When an issued card is used to make a purchase, an Issuing Authorization object is created. Authorizations must be approved for the purchase to be completed successfully.

      Related guide: Issued card authorizations

    • setOutboundPayment

      public void setOutboundPayment(OutboundPayment outboundPayment)
      Legacy OutboundPayments are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Outbound Payments instead of building a new v1 integration.

      Use OutboundPayments to send funds to another party's external bank account or FinancialAccount. To send money to an account belonging to the same user, use an OutboundTransfer.

      Simulate OutboundPayment state changes with the /v1/test_helpers/treasury/outbound_payments endpoints. These methods can only be called on test mode objects.

      Related guide: Moving money with Treasury using OutboundPayment objects

    • setOutboundTransfer

      public void setOutboundTransfer(OutboundTransfer outboundTransfer)
      Legacy OutboundTransfers are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Outbound Transfers instead of building a new v1 integration.

      Use OutboundTransfers to transfer funds from a FinancialAccount to a PaymentMethod belonging to the same entity. To send funds to a different party, use OutboundPayments instead. You can send funds over ACH rails or through a domestic wire transfer to a user's own external bank account.

      Simulate OutboundTransfer state changes with the /v1/test_helpers/treasury/outbound_transfers endpoints. These methods can only be called on test mode objects.

      Related guide: Moving money with Treasury using OutboundTransfer objects

    • setReceivedCredit

      public void setReceivedCredit(ReceivedCredit receivedCredit)
      Legacy ReceivedCredits are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Received Credits instead of building a new v1 integration.

      ReceivedCredits represent funds sent to a FinancialAccount (for example, via ACH or wire). These money movements are not initiated from the FinancialAccount.

    • setReceivedDebit

      public void setReceivedDebit(ReceivedDebit receivedDebit)
      Legacy ReceivedDebits are part of the v1 version of Treasury for platforms and do not support many of the features introduced in Treasury for platforms v2. Use Received Debits instead of building a new v1 integration.

      ReceivedDebits represent funds pulled from a FinancialAccount. These are not initiated from the FinancialAccount.

    • setType

      public void setType(String type)
      Type of the flow that created the Transaction. Set to the same value as flow_type.

      One of credit_reversal, debit_reversal, inbound_transfer, issuing_authorization, other, outbound_payment, outbound_transfer, received_credit, or received_debit.

    • equals

      public boolean equals(Object o)
      Overrides:
      equals in class Object

    • canEqual

      protected boolean canEqual(Object other)

    • hashCode

      public int hashCode()
      Overrides:
      hashCode in class Object