SourceTransaction
Some payment methods have no required amount that a customer must send. Customers can be instructed to send any amount, and it can be made up of multiple transactions. As such, sources can have multiple associated transactions.
Summary
Types
@type t() :: %Stripe.Resources.SourceTransaction{ ach_credit_transfer: term(), amount: term(), chf_credit_transfer: term(), created: term(), currency: term(), gbp_credit_transfer: term(), id: term(), livemode: term(), object: term(), paper_check: term(), sepa_credit_transfer: term(), source: term(), status: term(), type: term() }
ach_credit_transfer- Expandable.amount- A positive integer in the smallest currency unit (that is, 100 cents for $1.00, or 1 for ¥1, Japanese Yen being a zero-decimal currency) representing the amount your customer has pushed to the receiver.chf_credit_transfer- Expandable.created- Time at which the object was created. Measured in seconds since the Unix epoch. Format: Unix timestamp.currency- Three-letter ISO currency code, in lowercase. Must be a supported currency. Format: ISO 4217 currency code.gbp_credit_transfer- Expandable.id- Unique identifier for the object. Max length: 5000.livemode- If the object exists in live mode, the value istrue. If the object exists in test mode, the value isfalse.object- String representing the object's type. Objects of the same type share the same value. Possible values:source_transaction.paper_check- Expandable.sepa_credit_transfer- Expandable.source- The ID of the source this transaction is attached to. Max length: 5000.status- The status of the transaction, one ofsucceeded,pending, orfailed. Max length: 5000.type- The type of source this transaction is attached to. Possible values:ach_credit_transfer,ach_debit,alipay,bancontact,card,card_present,eps,giropay,ideal,klarna,multibanco,p24,sepa_debit,sofort,three_d_secure,wechat.