version: 2
models:
- name: stg_sf_user_role_data
  description: The table is about user roles in a system. It contains details like
    role name, developer name, access levels for different objects (case, contact,
    opportunity), forecast permissions, parent role, and portal type. Each role has
    a unique ID and additional flags for deletion and activity status. The table likely
    represents a hierarchical structure of user roles with varying permissions.
  columns:
  - name: is_deleted
    description: Indicates if the role has been deleted
    tests:
    - not_null
  - name: case_access_level
    description: Access level for case objects for account owners
    tests:
    - not_null
    - accepted_values:
        values:
        - No Access
        - Read Only
        - Read/Write
        - Full Access
        - fc4SIASWnVauLgJFy3VNNQ==
  - name: contact_access_level
    description: Access level for contact objects for account owners
    tests:
    - not_null
    - accepted_values:
        values:
        - No Access
        - Read Only
        - Read/Write
        - Full Access
        - Custom
        - fc4SIASWnVauLgJFy3VNNQ==
  - name: developer_name
    description: Unique identifier for developers to reference the role
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for developers to
        reference the role. For this table, each row represents a unique user role.
        The developer_name appears to be unique across rows in the sample data.
  - name: role_id
    description: Unique identifier for the role
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for the role. For
        this table, each row represents a unique user role. The role_id appears to
        be unique across rows in the sample data and is likely intended to be the
        primary key for this table.
  - name: can_manager_share_forecast
    description: Indicates if manager can share forecasts
    tests:
    - not_null
  - name: role_name
    description: Name of the role
    tests:
    - not_null
  - name: opportunity_access_level
    description: Access level for opportunity objects for account owners
    tests:
    - not_null
    - accepted_values:
        values:
        - No Access
        - Read Only
        - Read/Write
        - Full Access
        - fc4SIASWnVauLgJFy3VNNQ==
  - name: parent_role_id
    description: ID of the parent role in hierarchy
    tests:
    - not_null
  - name: portal_type
    description: Type of portal associated with the role
    tests:
    - not_null
    - accepted_values:
        values:
        - Customer
        - Employee
        - Partner
        - Vendor
        - Supplier
        - Investor
        - Public
        - Internal
        - External
        - Admin
        - Member
        - Guest
        - at+X+DrPZFPUpqSxBw83VA==
  - name: rollup_description
    description: Description for roll-up summary calculations
    tests:
    - not_null
  - name: is_active
    description: Indicates if the role is currently active
    tests:
    - not_null
  - name: forecast_user_id
    description: ID of the user responsible for forecasts
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_payout_data
  description: The table is about Stripe payouts. It contains details of individual
    payout transactions. Each row represents a payout with attributes like amount,
    currency, dates, status, and destination account. The table includes information
    on payout methods, source types, and transaction IDs. It also stores metadata
    and flags for automatic processing and live mode.
  columns:
  - name: payout_id
    description: Unique identifier for the payout
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column is a unique identifier for each payout transaction.
        For this table, each row represents a single payout, and payout_id is unique
        across rows.
  - name: payout_amount_cents
    description: Payout amount in cents
    tests:
    - not_null
  - name: is_automatic
    description: Indicates if payout was automatically scheduled
    tests:
    - not_null
  - name: balance_transaction_id
    description: Unique identifier for the balance transaction
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column appears to be a unique identifier for each balance
        transaction associated with a payout. For this table, each row represents
        a single payout, and balance_transaction_id is unique across rows.
  - name: currency_code
    description: Currency code of the payout
    tests:
    - not_null
  - name: description
    description: Brief description of the payout
    tests:
    - not_null
  - name: destination_bank_account_id
    description: ID of the destination bank account
    tests:
    - not_null
  - name: is_live_mode
    description: Indicates if payout was in live mode
    tests:
    - not_null
  - name: payout_method
    description: Method used for the payout
    tests:
    - not_null
    - accepted_values:
        values:
        - standard
        - express
        - wire transfer
        - check
        - direct deposit
        - paypal
        - cryptocurrency
        - prepaid card
        - cash
        - bank transfer
  - name: source_type
    description: Type of source for the payout
    tests:
    - not_null
    - accepted_values:
        values:
        - card
        - bank_account
        - cash
        - check
        - wire_transfer
        - paypal
        - venmo
        - cryptocurrency
        - other
  - name: payout_status
    description: Current status of the payout
    tests:
    - not_null
    - accepted_values:
        values:
        - in_transit
        - paid
        - pending
        - failed
        - canceled
        - reversed
        - completed
  - name: destination_type
    description: Type of payout destination
    tests:
    - not_null
    - accepted_values:
        values:
        - bank_account
        - credit_card
        - paypal
        - venmo
        - cash_app
        - check
        - wire_transfer
        - prepaid_card
        - cryptocurrency_wallet
        - mobile_money
  - name: connected_account_id
    description: ID of the connected Stripe account
    tests:
    - not_null
  - name: creation_timestamp
    description: Timestamp of payout creation
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents the exact time when the payout was created.
        While it's theoretically possible for two payouts to be created at the exact
        same second, it's highly unlikely in practice. For this table, each row represents
        a single payout, and creation_timestamp is likely to be unique across rows.
  - name: destination_card_id
    description: ID of the destination card (if applicable)
    tests:
    - not_null
  - name: estimated_arrival_date
    description: Estimated date of payout arrival
    tests:
    - not_null
  - name: failure_code
    description: Code indicating reason for payout failure
    tests:
    - not_null
  - name: failure_message
    description: Detailed message explaining payout failure
    tests:
    - not_null
  - name: failure_transaction_id
    description: Transaction ID if payout failed
    tests:
    - not_null
  - name: metadata
    description: Additional information in JSON format
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_transfer_data
  description: The table is about Stripe payouts. It includes details such as payout
    amount, currency, creation date, destination bank account, and transaction IDs.
    Each row represents a single payout. The table contains metadata fields, including
    references to NetSuite deposit IDs and links. All payouts are in USD and have
    not been reversed. The destination bank account is consistent across most entries.
  columns:
  - name: payout_id
    description: Unique identifier for the payout
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each payout. For
        this table, each row is for a single payout transaction. payout_id is unique
        across rows as it's specifically designed to be a unique identifier for each
        payout.
  - name: payout_amount_cents
    description: Payout amount in cents
    tests:
    - not_null
  - name: reversed_amount_cents
    description: Amount reversed in cents
    tests:
    - not_null
  - name: balance_transaction_id
    description: Unique identifier for the balance transaction
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each balance transaction
        associated with a payout. For this table, each row is for a single payout
        transaction. balance_transaction_id is unique across rows as it's specifically
        designed to be a unique identifier for each transaction.
  - name: currency
    description: Currency of the payout
    tests:
    - not_null
    - accepted_values:
        values:
        - usd
        - eur
        - gbp
        - jpy
        - cny
        - chf
        - cad
        - aud
        - nzd
        - inr
        - krw
        - sgd
        - hkd
        - mxn
        - brl
        - zar
        - sek
        - nok
        - dkk
        - rub
  - name: payout_description
    description: Brief description of the payout
    tests:
    - not_null
  - name: destination_bank_account_id
    description: Destination bank account identifier
    tests:
    - not_null
  - name: is_live_mode
    description: Indicates if the payout is live or test
    tests:
    - not_null
  - name: is_reversed
    description: Indicates if the payout was reversed
    tests:
    - not_null
  - name: payment_source_type
    description: Type of payment source
    tests:
    - not_null
    - accepted_values:
        values:
        - card
        - cash
        - bank transfer
        - digital wallet
        - cryptocurrency
        - check
        - money order
        - gift card
        - store credit
        - mobile payment
        - paypal
        - wire transfer
        - direct debit
        - prepaid card
  - name: destination_payment
    description: Unused field for destination payment
    tests:
    - not_null
  - name: destination_payment_id
    description: Unused field for destination payment ID
    tests:
    - not_null
  - name: metadata
    description: Additional information in JSON format
    tests:
    - not_null
  - name: payout_created_at
    description: Date and time of payout creation
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_refund_data
  description: The table is about refund data. It contains details of refund transactions.
    Each row represents a refund with attributes like ID, amount, currency, and status.
    It includes information on the associated charge, reason for refund, and timestamp.
    The table also stores metadata and receipt numbers for each refund. All refunds
    in the sample have succeeded status and are in USD currency.
  columns:
  - name: refund_id
    description: Unique identifier for the refund
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each refund. For
        this table, each row is for a single refund transaction. refund_id is unique
        across rows as it's designed to be a unique identifier for each refund.
  - name: refund_amount_cents
    description: Refund amount in cents
    tests:
    - not_null
  - name: balance_transaction_id
    description: Unique identifier for the balance transaction
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each balance transaction
        associated with the refund. For this table, each row is for a single refund
        transaction. balance_transaction_id is likely unique across rows as each refund
        would typically have its own balance transaction.
  - name: charge_id
    description: Unique identifier for the associated charge
    tests:
    - not_null
  - name: currency
    description: Currency of the refund
    tests:
    - not_null
  - name: refund_reason
    description: Reason for the refund
    tests:
    - not_null
    - accepted_values:
        values:
        - requested_by_customer
        - duplicate
        - item_not_received
        - item_defective
        - wrong_item_shipped
        - arrived_too_late
        - no_longer_needed
        - better_price_found
        - not_as_described
        - changed_mind
        - unauthorized_purchase
        - damaged_in_transit
        - quality_not_as_expected
        - missing_parts
        - incorrect_size
        - allergic_reaction
        - subscription_cancellation
        - technical_issues
        - pricing_error
        - product_recall
  - name: receipt_number
    description: Receipt number for the refund
    tests:
    - not_null
  - name: refund_status
    description: Current status of the refund
    tests:
    - not_null
    - accepted_values:
        values:
        - succeeded
        - pending
        - failed
        - cancelled
        - processing
        - reversed
  - name: failure_balance_transaction_id
    description: ID of failed balance transaction, if any
    tests:
    - not_null
  - name: failure_reason
    description: Reason for refund failure, if any
    tests:
    - not_null
  - name: metadata
    description: Additional information about the refund
    tests:
    - not_null
  - name: refund_created_at
    description: Timestamp of when the refund was created
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_fee_data
  description: The table is about fee transactions. It includes details such as the
    transaction ID, amount, currency, description, and type. All transactions are
    in USD. The amounts vary significantly, from 99 to 22215. Each transaction has
    a unique balance_transaction_id. The description and type fields contain consistent
    values across all entries, suggesting they might be category identifiers.
  columns:
  - name: transaction_id
    description: Unique identifier for the transaction
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each transaction.
        For this table, each row represents a distinct fee transaction. The transaction_id
        appears to be unique across rows, as each sample has a different value.
  - name: group_index
    description: Constant value, possibly for grouping
    tests:
    - not_null
  - name: amount_cents
    description: Transaction amount in cents
    tests:
    - not_null
  - name: currency_code
    description: Currency of the transaction
    tests:
    - not_null
  - name: category_hash
    description: Identifier or hash for transaction category
    tests:
    - not_null
  - name: type_hash
    description: Identifier or hash for transaction type
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_balance_transaction_data
  description: The table is about balance transactions. It includes details such as
    transaction ID, amount, date, currency, description, fees, net amount, source,
    status, and type. Each row represents a financial transaction like a charge or
    payout. The table tracks monetary movements, including both incoming (charges)
    and outgoing (payouts) transactions, with associated fees and net amounts.
  columns:
  - name: transaction_id
    description: Unique identifier for the transaction
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each transaction.
        For this table, each row is for a single financial transaction, and transaction_id
        is unique across rows.
  - name: transaction_amount_cents
    description: Transaction amount in cents
    tests:
    - not_null
  - name: currency_code
    description: Currency code of the transaction
    tests:
    - not_null
  - name: transaction_description
    description: Unique identifier or description of the transaction
    tests:
    - not_null
  - name: fee_amount_cents
    description: Fee amount in cents
    tests:
    - not_null
  - name: net_amount_cents
    description: Net amount after fees in cents
    tests:
    - not_null
  - name: transaction_source_id
    description: Source of the transaction (charge or payout ID)
    tests:
    - not_null
  - name: transaction_status
    description: Current status of the transaction
    tests:
    - not_null
    - accepted_values:
        values:
        - pending
        - completed
        - failed
        - cancelled
        - processing
        - rejected
        - on hold
        - refunded
        - partially refunded
  - name: transaction_type
    description: Type of transaction (charge or payout)
    tests:
    - not_null
    - accepted_values:
        values:
        - charge
        - payout
  - name: payout_id
    description: Identifier for the associated payout
    tests:
    - not_null
  - name: connected_account_id
    description: ID of the connected account (empty in this data)
    tests:
    - not_null
  - name: funds_available_date
    description: Date when the funds become available
    tests:
    - not_null
  - name: transaction_created_at
    description: Date and time when the transaction was created
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_dispute_data
  description: The table is about dispute data for charges. It includes details like
    dispute ID, amount, charge ID, currency, and dispute status. Evidence fields store
    information provided for the dispute. Metadata contains additional references.
    Key fields are reason for dispute, status (won/lost), and whether the charge is
    refundable. The table tracks dispute lifecycles from creation to resolution.
  columns:
  - name: dispute_id
    description: Unique identifier for the dispute
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column is a unique identifier for each dispute. For this
        table, each row represents a distinct dispute, and dispute_id is unique across
        rows.
  - name: dispute_transaction_id
    description: Transaction ID for the dispute
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents the transaction ID for each dispute. It
        appears to be unique for each dispute in the given sample, but it's possible
        that multiple disputes could theoretically be related to the same transaction
        in some cases.
  - name: charge_id
    description: Unique identifier for the disputed charge
    tests:
    - not_null
  - name: currency
    description: Currency of the disputed amount
    tests:
    - not_null
  - name: evidence_billing_address
    description: Billing address provided as evidence
    tests:
    - not_null
  - name: evidence_customer_email
    description: Customer email address provided as evidence
    tests:
    - not_null
  - name: evidence_customer_name
    description: Customer name provided as evidence
    tests:
    - not_null
  - name: evidence_purchase_ip
    description: Customer's IP address at purchase as evidence
    tests:
    - not_null
  - name: has_evidence
    description: Indicates if evidence has been submitted
    tests:
    - not_null
  - name: evidence_past_due
    description: Indicates if evidence submission is past due
    tests:
    - not_null
  - name: evidence_submission_count
    description: Number of evidence submissions
    tests:
    - not_null
  - name: evidence_receipt
    description: Receipt provided as evidence
    tests:
    - not_null
  - name: is_refundable
    description: Indicates if the charge can be refunded
    tests:
    - not_null
  - name: is_live
    description: Indicates if the dispute is in live mode
    tests:
    - not_null
  - name: dispute_reason
    description: Reason for the dispute
    tests:
    - not_null
    - accepted_values:
        values:
        - subscription_canceled
        - general
        - product_unacceptable
        - fraudulent_charge
        - duplicate_charge
        - product_not_received
        - incorrect_amount
        - unauthorized_charge
        - service_unsatisfactory
        - refund_not_processed
        - subscription_unwanted
        - quality_issue
        - shipping_issue
  - name: dispute_status
    description: Current status of the dispute
    tests:
    - not_null
    - accepted_values:
        values:
        - lost
        - won
        - pending
        - settled
        - withdrawn
  - name: additional_data
    description: Additional data related to the dispute
    tests:
    - not_null
  - name: connected_account_id
    description: ID of the connected account
    tests:
    - not_null
  - name: dispute_created_at
    description: Date and time when the dispute was created
    tests:
    - not_null
  - name: disputed_amount
    description: Disputed charge amount
    tests:
    - not_null
  - name: evidence_access_log
    description: Access activity log provided as evidence
    tests:
    - not_null
  - name: evidence_cancellation_disclosure
    description: Disclosure of cancellation policy as evidence
    tests:
    - not_null
  - name: evidence_cancellation_policy
    description: Cancellation policy provided as evidence
    tests:
    - not_null
  - name: evidence_cancellation_rebuttal
    description: Rebuttal to cancellation claim as evidence
    tests:
    - not_null
  - name: evidence_carrier
    description: Shipping carrier used for the order
    tests:
    - not_null
  - name: evidence_customer_signature
    description: Customer signature provided as evidence
    tests:
    - not_null
  - name: evidence_due_date
    description: Due date for submitting evidence
    tests:
    - not_null
  - name: evidence_duplicate_charge_docs
    description: Documentation for duplicate charge claim
    tests:
    - not_null
  - name: evidence_duplicate_charge_explanation
    description: Explanation for duplicate charge claim
    tests:
    - not_null
  - name: evidence_duplicate_charge_id
    description: ID of the duplicate charge
    tests:
    - not_null
  - name: evidence_ship_date
    description: Date the order was shipped
    tests:
    - not_null
  - name: evidence_ship_docs
    description: Documentation related to shipping
    tests:
    - not_null
  - name: evidence_tracking
    description: Tracking number for the shipped order
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_charge_data
  description: The table is about charge transactions. It contains details like amount,
    currency, customer ID, card details, and transaction status. Most charges failed
    due to card declines. The table includes information on the reason for failure,
    risk assessment, and metadata. All charges are in USD and were made on February
    18, 2021.
  columns:
  - name: charge_id
    description: Unique identifier for the charge
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each charge transaction.
        For this table, each row represents a distinct charge transaction. The charge_id
        is unique across rows.
  - name: amount_cents
    description: Transaction amount in cents
    tests:
    - not_null
  - name: refunded_cents
    description: Amount refunded in cents
    tests:
    - not_null
  - name: is_captured
    description: Whether the charge was captured
    tests:
    - not_null
  - name: card_id
    description: ID of the card used
    tests:
    - not_null
  - name: currency
    description: Currency of the charge
    tests:
    - not_null
    - accepted_values:
        values:
        - usd
        - eur
        - gbp
        - jpy
        - cad
        - aud
        - chf
        - cny
        - hkd
        - nzd
        - sek
        - krw
        - sgd
        - nok
        - mxn
        - inr
        - rub
        - zar
        - try
        - brl
        - twd
        - dkk
        - pln
        - thb
        - idr
  - name: customer_id
    description: ID of the customer
    tests:
    - not_null
  - name: description
    description: Description of the charge
    tests:
    - not_null
  - name: failure_code
    description: Code indicating reason for failure
    tests:
    - not_null
    - accepted_values:
        values:
        - card_declined
        - insufficient_funds
        - expired_card
        - invalid_card_number
        - invalid_cvc
        - incorrect_cvc
        - lost_card
        - stolen_card
        - fraudulent_card
        - processing_error
        - issuer_not_available
        - do_not_honor
        - card_not_supported
        - currency_not_supported
        - duplicate_transaction
        - authentication_required
        - blocked_card
        - restricted_card
        - card_velocity_exceeded
        - withdrawal_count_limit_exceeded
  - name: failure_message
    description: Message describing the failure
    tests:
    - not_null
  - name: is_live
    description: Whether charge was in live mode
    tests:
    - not_null
  - name: network_status
    description: Network status of the charge outcome
    tests:
    - not_null
    - accepted_values:
        values:
        - declined_by_network
        - approved
        - declined_by_issuer
        - network_error
        - timeout
        - invalid_card
        - insufficient_funds
        - lost_or_stolen_card
        - suspected_fraud
        - expired_card
        - processing_error
        - card_not_supported
        - card_restricted
        - do_not_honor
        - pickup_card
  - name: outcome_reason
    description: Reason for the charge outcome
    tests:
    - not_null
    - accepted_values:
        values:
        - do_not_honor
        - insufficient_funds
        - lost_card
        - stolen_card
        - expired_card
        - invalid_card_number
        - invalid_cvc
        - card_not_supported
        - processing_error
        - fraudulent
        - generic_decline
        - card_velocity_exceeded
        - suspected_fraud
        - card_restricted
        - currency_not_supported
        - approved
        - partially_approved
        - authentication_required
        - incorrect_address
        - transaction_not_allowed
  - name: risk_level
    description: Risk level of the charge outcome
    tests:
    - not_null
    - accepted_values:
        values:
        - low
        - normal
        - medium
        - high
        - critical
  - name: seller_message
    description: Seller message for the charge outcome
    tests:
    - not_null
    - accepted_values:
        values:
        - do_not_honor
        - insufficient_funds
        - lost_card
        - stolen_card
        - expired_card
        - invalid_card_number
        - invalid_cvc
        - card_declined
        - processing_error
        - incorrect_pin
        - incorrect_zip
        - invalid_expiry_date
        - card_not_supported
        - fraudulent
        - pickup_card
        - restricted_card
        - security_violation
        - service_not_allowed
        - transaction_not_allowed
        - try_again_later
        - The bank returned the decline code `do_not_honor`.
  - name: outcome_type
    description: Type of the charge outcome
    tests:
    - not_null
    - accepted_values:
        values:
        - issuer_declined
        - approved
        - blocked
        - expired_card
        - insufficient_funds
        - lost_card
        - stolen_card
        - invalid_amount
        - invalid_number
        - fraud_suspect
        - processor_declined
        - authentication_required
        - card_not_supported
        - do_not_honor
        - duplicate_transaction
        - generic_decline
  - name: is_paid
    description: Indicates if the charge was successful
    tests:
    - not_null
  - name: payment_intent_id
    description: Unique identifier for the payment intent
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for the payment intent
        associated with each charge. While it's likely to be unique for each transaction
        in this table, it's possible that multiple charges could be associated with
        the same payment intent in some cases.
  - name: hashed_receipt_email
    description: Hashed email address for receipt
    tests:
    - not_null
  - name: is_refunded
    description: Indicates if the charge was refunded
    tests:
    - not_null
  - name: charge_status
    description: Current status of the charge
    tests:
    - not_null
    - accepted_values:
        values:
        - failed
        - succeeded
        - pending
        - refunded
        - canceled
        - disputed
        - authorized
        - captured
        - expired
        - requires_payment_method
        - requires_confirmation
        - requires_action
        - processing
  - name: calculated_statement_descriptor
    description: ''
    tests:
    - not_null
  - name: created_at
    description: Timestamp of charge creation
    tests:
    - not_null
  - name: invoice_id
    description: ID of associated invoice
    tests:
    - not_null
  - name: metadata
    description: Additional metadata for the charge
    tests:
    - not_null
  - name: receipt_number
    description: Receipt number if available
    tests:
    - not_null
  - name: receipt_url
    description: URL to access the receipt
    tests:
    - not_null
  - name: shipping_address_1
    description: First line of shipping address
    tests:
    - not_null
  - name: shipping_address_2
    description: Second line of shipping address
    tests:
    - not_null
  - name: shipping_carrier
    description: Name of shipping carrier
    tests:
    - not_null
  - name: shipping_city
    description: City in shipping address
    tests:
    - not_null
  - name: shipping_country
    description: Country in shipping address
    tests:
    - not_null
  - name: shipping_phone
    description: Phone number for shipping
    tests:
    - not_null
  - name: shipping_postal_code
    description: Postal code in shipping address
    tests:
    - not_null
  - name: shipping_recipient_name
    description: Name of recipient for shipping
    tests:
    - not_null
  - name: shipping_state
    description: State in shipping address
    tests:
    - not_null
  - name: shipping_tracking_number
    description: Tracking number for shipment
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_payment_intent_data
  description: The table is about payment intents. It includes details such as amount,
    currency, customer ID, payment method ID, and status. Each row represents a single
    payment intent with a unique ID. The table tracks information like creation date,
    capture method, and whether the payment succeeded. It also includes fields for
    errors and cancellations, though most are empty in these samples.
  columns:
  - name: payment_intent_id
    description: Unique identifier for the payment intent
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each payment intent.
        For this table, each row is for a single payment intent, and payment_intent_id
        is unique across rows.
  - name: amount_in_cents
    description: Payment amount in the smallest currency unit
    tests:
    - not_null
  - name: amount_capturable
    description: Amount available for capture
    tests:
    - not_null
  - name: amount_received
    description: Amount actually received
    tests:
    - not_null
  - name: application
    description: Associated application for the payment
    tests:
    - not_null
  - name: capture_method
    description: Method used to capture payment
    tests:
    - not_null
    - accepted_values:
        values:
        - automatic
        - manual
        - card
        - bank_transfer
        - cash
        - check
        - paypal
        - apple_pay
        - google_pay
        - cryptocurrency
        - wire_transfer
        - direct_debit
        - invoice
  - name: confirmation_method
    description: Method used to confirm payment
    tests:
    - not_null
    - accepted_values:
        values:
        - automatic
        - manual
        - email
        - sms
        - phone call
        - in-app notification
        - bank statement
        - receipt
        - invoice
        - credit card statement
        - payment gateway confirmation
        - third-party verification
  - name: currency_code
    description: Currency code for the payment
    tests:
    - not_null
  - name: customer_id
    description: Unique identifier for the customer
    tests:
    - not_null
  - name: description
    description: Description of the payment intent
    tests:
    - not_null
  - name: is_live
    description: Whether the payment is live or test
    tests:
    - not_null
  - name: payment_method_id
    description: ID of the payment method used
    tests:
    - not_null
  - name: receipt_email
    description: Email address for receipt
    tests:
    - not_null
  - name: status
    description: Current status of the payment intent
    tests:
    - not_null
    - accepted_values:
        values:
        - succeeded
        - processing
        - requires_payment_method
        - requires_confirmation
        - requires_action
        - canceled
        - requires_capture
  - name: canceled_at
    description: Timestamp of cancellation
    tests:
    - not_null
  - name: cancellation_reason
    description: Reason for cancellation if applicable
    tests:
    - not_null
  - name: created_at
    description: Timestamp of payment intent creation
    tests:
    - not_null
  - name: decline_code
    description: Decline code if payment was declined
    tests:
    - not_null
  - name: error_charge_id
    description: ID of charge with last error
    tests:
    - not_null
  - name: error_code
    description: Error code of last failed attempt
    tests:
    - not_null
  - name: error_doc_url
    description: URL to error documentation
    tests:
    - not_null
  - name: error_message
    description: Error message for last failed attempt
    tests:
    - not_null
  - name: error_param
    description: Parameter that caused the error
    tests:
    - not_null
  - name: error_source_id
    description: ID of source causing the error
    tests:
    - not_null
  - name: error_type
    description: Type of the last error
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_payment_method_card_data
  description: The table is about payment method card details. It includes unique
    payment method IDs, a consistent brand identifier, and fingerprints for each card.
    The funding type is specified as credit for all entries. Some fields like charge_id,
    description, type, and wallet_type are empty. The table appears to store essential
    information for credit card payment methods.
  columns:
  - name: payment_method_id
    description: Unique identifier for the payment method
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each payment method.
        For this table, each row represents a distinct payment method, and the payment_method_id
        appears to be unique across rows.
  - name: payment_provider_id
    description: Identifier for the payment provider or card issuer
    tests:
    - not_null
  - name: card_fingerprint
    description: Unique identifier for the specific card
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each specific
        card. For this table, each row represents a distinct payment method, and the
        card_fingerprint appears to be unique across rows.
  - name: funding_type
    description: Type of funding source for the payment method
    tests:
    - not_null
    - accepted_values:
        values:
        - credit
        - debit
        - cash
        - check
        - wire transfer
        - cryptocurrency
        - gift card
        - store credit
        - loyalty points
        - prepaid card
        - mobile payment
        - bank transfer
  - name: digital_wallet_type
    description: Specifies the digital wallet used, if applicable
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_card_data
  description: The table is about payment methods. It contains details such as card
    ID, brand, country, currency, expiration date, last 4 digits, funding type, and
    creation date. Each row represents a unique payment method with its associated
    attributes. The table includes metadata and checks for address and CVC. Most fields
    are related to card information and payment processing details.
  columns:
  - name: issuing_country
    description: Country where the payment method was issued
    tests:
    - not_null
  - name: expiration_year
    description: Expiration year of the payment card
    tests:
    - not_null
  - name: currency
    description: Currency associated with the payment method
    tests:
    - not_null
  - name: payment_method_id
    description: Unique identifier for the payment method
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each payment method.
        For this table, each row represents a distinct payment method, and the payment_method_id
        appears to be unique across rows.
  - name: expiration_month
    description: Expiration month of the payment card
    tests:
    - not_null
  - name: payment_network
    description: Payment network processing the transaction
    tests:
    - not_null
    - accepted_values:
        values:
        - Visa
        - Mastercard
        - American Express
        - Discover
        - JCB
        - UnionPay
        - Diners Club
        - PayPal
        - Stripe
        - Square
        - Alipay
        - WeChat Pay
        - Apple Pay
        - Google Pay
        - Samsung Pay
        - Interac
        - Klarna
        - Affirm
        - Afterpay
        - Venmo
        - 553f65f270c86a4a05c964dc20e8cc70
  - name: funding_type
    description: Funding type of the payment method (e.g., credit, debit)
    tests:
    - not_null
    - accepted_values:
        values:
        - credit
        - debit
        - prepaid
        - gift card
        - bank transfer
        - cash
        - check
        - cryptocurrency
        - mobile payment
        - wire transfer
        - loyalty points
        - store credit
  - name: card_brand
    description: Brand or network of the payment card
    tests:
    - not_null
    - accepted_values:
        values:
        - Visa
        - Mastercard
        - American Express
        - Discover
        - JCB
        - Diners Club
        - UnionPay
        - Maestro
        - Visa Electron
        - China T-Union
        - RuPay
        - InterPayment
        - InstaPayment
        - UATP
        - Dankort
        - Mir
        - Troy
        - Elo
        - Hipercard
        - BC Card
        - 553f65f270c86a4a05c964dc20e8cc70
  - name: is_deleted
    description: Indicates if the payment method has been deleted
    tests:
    - not_null
  - name: cvc_verification
    description: Status of the Card Verification Code check
    tests:
    - not_null
    - accepted_values:
        values:
        - pass
        - fail
        - not_checked
  - name: card_fingerprint
    description: Unique identifier for the card number
    tests:
    - not_null
  - name: creation_datetime
    description: Date and time when the payment method was created
    tests:
    - not_null
  - name: last4_digits
    description: Last 4 digits of the payment card number
    tests:
    - not_null
  - name: metadata
    description: Additional information stored as key-value pairs
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_payment_method_data
  description: The table is about payment method data. It contains details like ID,
    billing information, customer ID, and payment type. Billing details include address,
    email, name, and phone, but most fields are empty or encrypted. All entries are
    for card payments in live mode. The table tracks payment methods associated with
    customers, including creation date and unique identifiers.
  columns:
  - name: billing_postal_code
    description: Postal code of the billing address (encrypted)
    tests:
    - not_null
  - name: payment_method_id
    description: Unique identifier for the payment method
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each payment method.
        For this table, each row represents a distinct payment method, and payment_method_id
        is unique across rows.
  - name: billing_name
    description: Name associated with the billing details (encrypted)
    tests:
    - not_null
  - name: payment_method_type
    description: Type of payment method (e.g., card)
    tests:
    - not_null
    - accepted_values:
        values:
        - card
        - cash
        - bank transfer
        - check
        - digital wallet
        - cryptocurrency
        - mobile payment
        - wire transfer
        - money order
        - debit card
        - credit card
        - prepaid card
        - ACH
        - PayPal
        - Venmo
        - Apple Pay
        - Google Pay
        - gift card
        - store credit
  - name: customer_id
    description: Unique identifier for the customer
    tests:
    - not_null
  - name: billing_email
    description: Email address for billing (encrypted)
    tests:
    - not_null
  - name: is_live
    description: Indicates if the payment method is in live mode
    tests:
    - not_null
  - name: billing_address_1
    description: First line of the billing address
    tests:
    - not_null
  - name: billing_address_2
    description: Second line of the billing address
    tests:
    - not_null
  - name: billing_city
    description: City of the billing address
    tests:
    - not_null
  - name: billing_country
    description: Country of the billing address
    tests:
    - not_null
  - name: billing_state
    description: State of the billing address
    tests:
    - not_null
  - name: created_at
    description: Date and time the payment method was created
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_subscription_data
  description: The table is about subscription data. It contains details of individual
    subscriptions, including billing information, subscription status, customer ID,
    and pricing details. Key fields include subscription ID, billing cycle dates,
    cancellation info, customer ID, subscription status, and trial period dates. The
    metadata field stores additional custom information like external IDs.
  columns:
  - name: subscription_id
    description: Unique identifier for the subscription
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each subscription.
        For this table, each row represents a distinct subscription, and subscription_id
        should be unique across rows.
  - name: billing_method
    description: Billing type or method for the subscription
    tests:
    - not_null
    - accepted_values:
        values:
        - Credit Card
        - Debit Card
        - PayPal
        - Bank Transfer
        - Cash
        - Check
        - Apple Pay
        - Google Pay
        - Cryptocurrency
        - Invoice
        - Direct Debit
        - Wire Transfer
        - fdfjk
        - fdsiew
  - name: billing_threshold_amount
    description: Minimum amount to trigger a billing event
    tests:
    - not_null
  - name: reset_billing_cycle_on_threshold
    description: Indicates if billing cycle resets on threshold
    tests:
    - not_null
  - name: cancel_at_period_end
    description: Indicates if subscription cancels at period end
    tests:
    - not_null
  - name: customer_id
    description: Unique identifier for the customer
    tests:
    - not_null
  - name: days_until_due
    description: Number of days until payment is due
    tests:
    - not_null
  - name: default_payment_source_id
    description: ID of the default payment source
    tests:
    - not_null
  - name: is_live_mode
    description: Indicates if the subscription is in live mode
    tests:
    - not_null
  - name: subscription_quantity
    description: Quantity of the subscribed item or service
    tests:
    - not_null
  - name: subscription_status
    description: Current status of the subscription
    tests:
    - not_null
    - accepted_values:
        values:
        - active
        - inactive
        - pending
        - cancelled
        - expired
        - suspended
        - trialing
        - past_due
        - unpaid
        - on_hold
  - name: application_fee_percentage
    description: Percentage of the application fee charged
    tests:
    - not_null
  - name: billing_cycle_start
    description: Date/time when the billing cycle starts
    tests:
    - not_null
  - name: cancellation_date
    description: Date/time when the subscription was canceled
    tests:
    - not_null
  - name: creation_date
    description: Date/time when the subscription was created
    tests:
    - not_null
  - name: current_period_end
    description: End date/time of the current billing period
    tests:
    - not_null
  - name: current_period_start
    description: Start date/time of the current billing period
    tests:
    - not_null
  - name: end_date
    description: Date/time when the subscription ended
    tests:
    - not_null
  - name: metadata
    description: Additional custom information about the subscription
    tests:
    - not_null
  - name: scheduled_cancellation_date
    description: Scheduled date/time for subscription cancellation
    tests:
    - not_null
  - name: subscription_start_date
    description: Date/time when the subscription started
    tests:
    - not_null
  - name: tax_percentage
    description: Percentage of tax applied to the subscription
    tests:
    - not_null
  - name: trial_end_date
    description: End date/time of the trial period
    tests:
    - not_null
  - name: trial_start_date
    description: Start date/time of the trial period
    tests:
    - not_null
  tests: []

version: 2
models:
- name: stg_plan_data
  description: The table is about subscription plans. It contains details like plan
    ID, active status, pricing amount, currency, billing interval, created date, and
    product ID. Each row represents a unique plan with its specific attributes. The
    plans have different durations (monthly or multi-month) and prices. All plans
    use USD currency and are set to "licensed" usage type.
  columns:
  - name: plan_id
    description: Unique identifier for the plan
    tests:
    - not_null
    - unique
    cocoon_meta:
      unique_reason: This column represents a unique identifier for each subscription
        plan. For this table, each row represents a distinct subscription plan. The
        plan_id appears to be unique across rows, as it uses a specific alphanumeric
        format (e.g., zbc001, abc002) that is likely designed to be unique for each
        plan.
  - name: is_active
    description: Indicates if the plan is currently active
    tests:
    - not_null
  - name: price_in_cents
    description: Price of the plan in cents
    tests:
    - not_null
  - name: billing_method
    description: Method used for billing calculation
    tests:
    - not_null
    - accepted_values:
        values:
        - per_unit
        - flat_rate
        - tiered
        - usage_based
        - subscription
        - value_based
        - time_and_materials
        - milestone
        - cost_plus
        - percentage_of_completion
  - name: currency_code
    description: Currency used for the plan pricing
    tests:
    - not_null
  - name: billing_interval
    description: Billing frequency (e.g., month)
    tests:
    - not_null
    - accepted_values:
        values:
        - day
        - week
        - month
        - quarter
        - year
  - name: billing_cycle_duration
    description: Number of intervals between billings
    tests:
    - not_null
  - name: is_deleted
    description: Indicates if the plan has been deleted
    tests:
    - not_null
  - name: is_live_mode
    description: Indicates if the plan is in live or test mode
    tests:
    - not_null
  - name: product_id
    description: Unique identifier of the associated product
    tests:
    - not_null
  - name: usage_type
    description: Type of usage for the plan
    tests:
    - not_null
    - accepted_values:
        values:
        - licensed
        - subscription
        - pay-per-use
        - freemium
        - perpetual
        - tiered
        - metered
        - floating
        - site
        - volume
        - concurrent
        - named-user
        - enterprise
        - academic
        - trial
  - name: creation_datetime
    description: Date and time when the plan was created
    tests:
    - not_null
  - name: plan_nickname
    description: Optional nickname for the plan (empty in this case)
    tests:
    - not_null
  - name: pricing_tier_mode
    description: Pricing tier structure (empty in this case)
    tests:
    - not_null
  - name: trial_period_days
    description: Number of trial days (empty in this case)
    tests:
    - not_null
  - name: usage_aggregation_method
    description: Aggregation method for metered usage (empty in this case)
    tests:
    - not_null
  - name: usage_transform_divisor
    description: Usage transformation divisor (empty in this case)
    tests:
    - not_null
  - name: usage_transform_rounding
    description: Usage transformation rounding method (empty in this case)
    tests:
    - not_null
  tests: []