Cobre Keys do not have an expiration date, so they can be used as many times as needed to receive payins.
| Account Type | Geo | Key Type | Key Value Example |
|---|---|---|---|
| Cobre Balance | COL | Alphanumeric | @CBARG452PEXTOCOLOMBI |
| Financial Institution Prefix | Random String | Configurable String |
|---|---|---|
| @CB — Identifies keys created by Cobre | Ensures global uniqueness | Allows the client to personalize the key based on name, ID, or a random value |
The alias used for name-based keys can be configured from the Cobre Portal or through a request via our support channels.
| Key Type | Length | Example |
|---|---|---|
name | 21 | @CBARG452PEXTOCOLOMBI |
id | 17-18 | @CBAQ1ER9001234567 |
random | 10 | @CBAQ1EXD8 |
open_input | 21 | @MYPERSONALIZEDKEY123 |
open_input: Only letters and numbers allowed, no spaces, min 5 characters and max 20 for the customizable part. name: You can create name-type keys with your alias at the beginning to enhance your brand visibility in the generated keys. For example: @PEXTOCOLOMBICBARG452 Please contact your KAM to enable some of these features.
| Payment Method | open_input | name | id | random |
|---|---|---|---|---|
| Direct link Key | x | x | ||
| Direct link QR | x | |||
| Checkout Key | x | |||
| Checkout QR | x | |||
| Static Key | x | x | x | x |
| Status | Description |
|---|---|
processing | An intermediate state indicating that the submitted Cobre key creation is still being processed |
registered | The Cobre key was successfully created and registered, and is now available for use |
unregistered | The Cobre key was cancelled at the user’s request via our key cancellation API.** Once cancelled, a key cannot be reactivated** |
disabled | The Cobre key was disabled either by the user or by Cobre. A key in the disabled state can be reactivated |
failed | The attempted action on the key was unsuccessful and it is necessary to submit the creation request again |
Keep in mind that Cobre key creation is asynchronous, so creation requests will always return in processing status. The final status of the key must be checked later through the obtain all keys endpoint or obtain one specific endpoint, and therefore the fields key_value and source_id will only be returned once the key transitions to the registered status.
At this time, only one Cobre Key can be created per Cobre Balance account.