---
title: "get customer · RUAL Documentation"
description: "Reads a Stripe customer. A customer deleted in Stripe comes back as a tombstone rather than an error : this block reports that as CUSTOMER_DELETED inste…"
canonical: https://docs.rual.nl/block-types/stripe/stripeconnection_customers_get
language: en
---

# get customer

This block is part of the [`stripe`](https://docs.rual.nl/block-types/stripe) group and was last modified in core [`v15.0.0`](https://docs.rual.nl/core-versions/150000).

Reads a Stripe customer. A customer deleted in Stripe comes back as a tombstone rather than an error : this block reports that as `CUSTOMER_DELETED` instead of handing back an almost-empty object that looks live.

- flow `flow`

- connection required `stripeconnection`

- customer id required `value`

- flow `flow`

- connection `stripeconnection`

- customer id `value` cus_… : store this on your own user record.

- email `value`

- name `value`

- balance `number` Stripe's sign convention is the opposite of the intuitive one: **negative is credit the customer holds**, positive is what they owe.

- currency `value`

- meta data `object`

- customer `object`

- success `condition`

- error `value` Stripe's own message, or a sentinel like MISSING_SESSION_ID for a problem in the wiring.

- error code `value` Stripe's machine-readable code, e.g. `card_declined`, `resource_missing`.

- decline code `value` Why the bank refused, e.g. `insufficient_funds`. Only set on a declined card.

| `stripe customer` |
| --- |
| `customer balance` |

### Version history

Introduced in [`v15.0.0`](https://docs.rual.nl/core-versions/150000).

### Service documentation