Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SEP-9: add clabe_number #1202

Merged
merged 3 commits into from
May 13, 2022
Merged

SEP-9: add clabe_number #1202

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c26eecd
SEP-9: add `clabe_number`
JakeUrban May 13, 2022
f16f65b
add PR link to changelog
JakeUrban May 13, 2022
4a3e096
Update ecosystem/sep-0009.md
JakeUrban May 13, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions ecosystem/sep-0009.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ Title: Standard KYC Fields
Author: stellar.org
Status: Active
Created: 2018-07-27
Updated: 2022-01-03
Version 1.5.0
Updated: 2022-05-13
Version 1.6.0
```

## Simple Summary
Expand Down Expand Up @@ -65,6 +65,7 @@ Name | Type | Description
`bank_number` | string | Number identifying bank in national banking system (routing number in US)
`bank_phone_number` | string | Phone number with country code for bank
`bank_branch_number` | string | Number identifying bank branch
`clabe_number` | string | Bank account number for Mexico
`tax_id` | string | Tax identifier of user in their country (social security number in US)
`tax_id_name` | string | Name of the tax ID (`SSN` or `ITIN` in the US)
`occupation` | number | Occupation ISCO code
Expand Down Expand Up @@ -109,3 +110,6 @@ Name | Type | Description

Address formatting varies widely from country to country and even within each country. See [here](https://stackoverflow.com/questions/11160192/how-to-parse-freeform-street-postal-address-out-of-text-and-into-components) for details. Rather than attempting to create a field for each possible part of an address in every country, this protocol takes a middle of the road approach. Address fields that are fairly universal can be encoded with the `country_code`, `state_or_province`, `city`, and `postal_code` fields. Full addresses, however, should be encoded as a single multi-line string in the `address` field. This allows any address in the world to be represented with a limited number of fields. If address parsing is necessary, parsing will be easier since the country, city, and postal code are already separate fields.

## Changelog

* `v1.6.0`: Add `clabe_number` to Natural Person KYC fields ([#1202](https://github.com/stellar/stellar-protocol/pull/1202)).