Stripe Financial Address

The details are a Stripe object, not a bank account you own

The mental model that causes trouble is treating a financial address as a bank account in your name at a bank you chose. It is a set of credentials issued by Stripe, attached to a Stripe balance, and managed through Stripe.

That has one immediate consequence for your books. Money arriving at the address does not land in your bank. It lands in a Stripe balance that happens to be reachable by bank rails. Nothing has reached your business current account, and nothing will until you move it, which is a separate movement with its own record.

The second consequence is the plural. Because a financial account can carry several addresses, the right question during reconciliation is not "did money arrive at my Stripe account number" but "which address did it arrive at". Stripe exposes the addresses through create, retrieve and list operations, and each one names the financial account it corresponds to, so the mapping from address back to balance is always recoverable.

Credentials only exist once the address is active

A financial address carries a status, and Stripe documents four values.

Pending means the address is being created. Active means it is usable. Archived means, in Stripe’s words, that the address is archived and it cannot be used anymore. Failed means the creation of the address did not succeed.

The credentials object is where the real banking details sit, and Stripe is explicit that it is only available for addresses with an active status. This is the detail most likely to catch someone out. An address in the pending state exists, has an identifier, and can be retrieved through the API, and it has no account number on it. There is nothing to send a customer, and nothing to put on an invoice, until the status moves to active.

Failed is worth treating as its own case rather than as a slow version of pending. It is not a stage on the way to active. It is an outcome, and it means the address has to be created again rather than waited on. Since both states look like the absence of usable details from the outside, reading the status field is what tells you whether you are waiting or whether you have work to do.

Two currency fields, and why they are not the same question

A financial address carries two separate currency fields, and the distinction between them is easy to miss because the names are so close.

Stripe defines the first as the currency the financial address supports. That is the currency somebody can send to it. The second is described as the currency the financial address settles into the financial account, and it is nullable.

Read together, those two fields allow for an address that accepts money in one currency and credits your balance in another. For anyone keeping books, that is a conversion happening inside Stripe, between the moment the payer sent the money and the moment it appeared in your balance.

The practical rule that follows is simple and worth stating plainly: the amount your customer sent and the amount your balance received are two different figures whenever those currencies differ, and the one your books need is the one that actually landed. Take it from the credit recorded on the Stripe side rather than from the remittance advice your customer sends you, because only the first one knows what rate was applied.

Retiring an address is not the same as retracting it

Archiving is how a financial address is taken out of service, and Stripe is direct about the effect: an archived address cannot be used anymore.

What archiving cannot do is reach the places the address has already been. Bank details spread. They sit in a customer’s accounts payable system, in a saved payee, on a signed contract, in a supplier onboarding form filled in eighteen months ago. Retiring the address at Stripe changes Stripe’s side of that relationship and changes nothing about the copies.

Stripe’s reference for the object states what the archived status means. It does not state what becomes of funds someone sends to an archived address afterwards, and that is not a question worth answering by reasoning about how bank rails usually behave. If you are planning to retire an address that customers have been paying into, confirm the handling with Stripe first, and get the new details to every payer before the old address is archived rather than after.

What actually shows up in your books is the credit, not the address

The address is the destination. It is not the event, and it is not the thing your accounting records.

When money arrives over bank rails at a financial address, the object Stripe writes is a received credit, and on a received credit of that type the address is one of the details carried alongside the originating bank information. So the address is metadata on the arrival rather than the arrival itself.

That is the right division of labour for reconciliation too. The address answers "where was this sent". The received credit answers "how much arrived, in which currency, and when", which is the set of facts a journal entry is built from. If you are tracing a payment that a customer insists they sent, the address tells you whether they aimed at the right place, and the credit tells you whether anything landed.