RailbedDocs

Understand your customers

See a customer's order history, contact details and spending. Keep a private note and manage the personal data saved in Railbed.

On this page

How customers appear

Customers brings together purchases associated with the same email address in the current mode. Railbed creates a customer when a checkout or store order provides an email. You do not need to enter each customer by hand.

Email matching ignores letter case. Test and Live records are separate. Names, phone numbers and addresses appear when the checkout or connected source supplies them. Later orders can update those saved details; omitted details keep their earlier value.

A customer first created when a buyer starts payment may contain only their email. Open the order to inspect any additional addresses or details supplied with the purchase.

Find a customer

  1. Open Customers and check the mode.
  2. Search by name, email or phone. You can also use the customer's full ID.
  3. Choose a view to narrow the list, then open a customer to see their details.
ViewWhat it means
AllCustomers matching the current search
ReturningAt least two paid orders
NewFirst seen in the last 30 days
Never paidNo paid orders yet

Sort by recent activity or Spent using the list's column controls. The Spent sort compares spending on a USD basis; displayed amounts retain their original currencies. They are not a converted wallet balance.

Choose Show more when more records are available. If nothing matches, use Clear filters and check whether the customer belongs to the other mode.

Read the customer page

The page links the person to their orders and the information supplied with them:

  • Spent: the amounts of their paid payment attempts, grouped by currency. Unpaid attempts are not included. If the buyer paid twice for one order, both paid amounts count here even though there is still one order.
  • Reached your wallet: reported net receipts in USDC from their payment activity. This can differ from Spent because of fees, conversion, unreported receipts or multiple attempts.
  • Orders: the number of paid orders alongside all their orders, with a compact history of payment outcomes.
  • Needs you: a shortcut to an order needing payment review or fulfilment among the orders shown.
  • Contact and address: available email, phone, source-store customer IDs and the latest saved shipping or billing address.

Open an order to inspect its items, payment attempts and timeline without leaving the customer page. For a long history, All their orders opens the Orders list filtered to that customer. The detail page shows the latest 50 orders first.

Email opens your device's email app with the customer's address. It does not send a message by itself. Copy address copies the displayed address for use in your delivery workflow.

Keep a private note

Use the Note card for context that helps you serve the customer, such as a preferred delivery instruction. The customer never sees this note, and it is not included in API customer responses or merchant webhooks.

Choose Add note or Edit note, write up to 2,000 characters, then Save note. Cancel keeps the saved version. Clearing the text and saving removes the note.

The note belongs to this Railbed record. It does not update your store's customer profile, and changes to a store profile do not edit this private note.

Export your customer list

Choose Export CSV on Customers. It follows the current search, view and sort, and exports up to 10,000 records. The file includes available contact details, order counts, spending by currency, reported USDC receipts and customer IDs.

Deleted customers are left out of the customer list and its export. Previously downloaded files remain wherever you saved them.

Delete customer data

Open the customer, choose Delete customer data, then read the confirmation carefully. This action cannot be undone.

It removes the saved name, email, phone, addresses, store customer identifiers and private note from the customer record, and removes the associated personal-detail fields from orders, payments and stored webhook delivery bodies. Orders, payment records and amounts remain for your records, with the person shown as Deleted customer.

After deletion:

  • The customer leaves the normal customer list. Existing order links can still show the anonymized record.
  • The same email in a future purchase creates a new customer record.
  • Webhooks already delivered, emails sent and files exported cannot be recalled. Handle those copies in the systems where they were saved.
  • Custom order descriptions, references and integration metadata are separate fields. Do not assume they have been scrubbed if you or an integration placed personal information in them.

Deleting customer data does not refund, cancel or fulfil an order. Review the relevant order or payment separately if the buyer also needs help with a purchase.

Updated · This page as Markdown