Performing Searches in the Dashboard

    Use the Dashboard to search for payments, customers, and more.

    You can use the advanced search mechanism available in the Dashboard to look up information about:

    • Connected accounts
    • Coupons
    • Customers
    • Invoices and invoice items
    • Orders
    • Payments
    • Payouts
    • Plans
    • Products
    • Sources
    • Transfers

    When you perform a search, the top results appear immediately and you can view all matches either by clicking Show more results or pressing Enter. You can use different pieces of information as search terms, such as the the last four digits of a card or bank account (e.g., 4242), type of payment method (e.g., ideal), business name of a connected Stripe account (e.g., Rocketship), or email receipt number (e.g., 1817-9523).

    For searches using dates, you can provide them in different formats, such as 09/19, 2019/09, or 2019-09-13. You can also use object identifiers (e.g., a dispute ID) to take you directly to the object you’re looking for.

    No additional context is necessary for most searches. The Dashboard automatically looks for the most relevant information based on your search query. You can make use of search filters and operators for more granular control.

    Search filters and operators

    By default, the Dashboard looks for values that match your search term in the most logical fields within objects (e.g., an email address in the email field or description, or a date as a card expiration date). You can use filters and operators to further refine your searches. The more terms you provide in your search query, the fewer the number of results.

    Use filters to limit your search terms so they only apply to specific fields within applicable objects. Preface a search term with one of these filters. Many fields are shared across different objects. For instance, amount applies to payments, invoices, payouts, etc.

    Search filter Description Example
    amount: The amount of an object. For decimal currencies, use a decimal point for both currency units (e.g., dollars and cents). amount:149.99
    brand: The brand of card associated with an object. brand:visa
    country: The two-letter ISO code representing the country associated with an object. country:GB
    created: The date an object was created. created:2017/08/24
    currency: The three-letter ISO code representing the currency of an object. currency:EUR
    email: The email (either full address or part of one) of an object. email:jenny.rosen@example.com
    exp: The expiration date of the card associated with an object. exp:09/19
    flow: The type of flow for customer action that applies to a Sources payment. flow:redirect
    last4: The last four digits of the card associated with an object. last4:4080
    metadata: Metadata value on a supported object. Additional search options for metadata are also available. metadata:555-5555
    name: The cardholder or customer name associated with an object. name:jenny
    postal: The ZIP code associated with an object. postal:12345
    receipt: The receipt number used in a payment or refund email receipt. receipt:3330-2392
    risk_level: The risk level of a payment determined by Radar. risk_level:elevated
    status: The status of an object. status:canceled
    type: The type of payment method used for a Sources payment. type:ideal
    usage: The usage availability of a Sources payment method. usage:single_use
    zip: The ZIP code associated with an object. zip:12345

    You can use these operators when searching for amounts and dates to refine your search to a particular range.

    Operator Description Example
    > Greater than an amount, or after the specified date. amount:>149.99
    < Less than an amount, or before the specified date. date:<2017-08-24
    .. Within a range of dates or amounts. amount:50.00..99.99

    You can also use the Boolean operators is: and not: with these payment-specific operators.

    Operator Description Example
    charge A payment is:charge
    captured A payment that has been captured not:captured
    disputed A payment that has been disputed is:disputed
    paid A payment or invoice that has been paid is:paid
    refunded A payment or invoice that has been refunded not:refunded

    Combining and negating search terms

    You can use more than one search term to narrow down your search and reduce the number of results. You can also negate any search term, so that matches for it are not included by prefacing the term with a hyphen -.

    Example Description
    last4:4242 exp:09/19 The last four digits of the card are 4242 and expiration date is 09/19.
    last4:4242 -exp:09/19 The last four digits of the card are 4242 and expiration date is not 09/19.
    type:ideal status:canceled iDEAL payments where the source has been canceled and a payment was not completed.

    Metadata searches

    You can perform searches on metadata that you have added to objects that support it (e.g., payments). Metadata values are automatically included during a search for any text that does not use a filter.

    You can use the metadata: filter so the search term only looks up metadata values. To search for a specific metadata key-value pair, use the metadata key name as a filter, such as order_id:xyn712.

    Best practices

    Many searches can be performed with a single search term. Use something that would be fairly atypical, such as a name or email address. If you are seeing too few results, make the search term less specific. If there are too many results, include additional terms, one at a time.

    Use a wider range of values when using dates or amounts as search terms. Currency conversions and time zone differences between you and your customer are a common source of confusion when looking up information about a payment. Use additional search terms or even different ones altogether.

    As search terms are included in the URL, you can bookmark the search or share it with other team members as you would any other web page.