Get Account

Retrieves detailed information about a specific counterparty account, including comprehensive bank details, crypto wallet information, counterparty and customer relationships, and account status.

Endpoint

GET/v2/counterparty/account/{accountId}

Link

Gateway APIstagep.tst-apidmndelss.com

Request

Path Parameters

Parameter	Type	Description	Required	Example
accountId	string	Account ID to retrieve details for.	Yes	"UvYqyrDwqI"

Headers

Key	Value	Required
Authorization	123	Yes
Accept	application/json	Yes

---

Response (200 OK)

Returns a complete account object with all associated details including bank information, crypto details, and relationship information.

Response Fields

1. Account Information

Field	Type	Description	Example
accountId	string	Unique account identifier.	"UvYqyrDwqIn1"
currencyCode	string	Currency code (ISO 4217).	"USD"
status	string	Current account status.	"ACCEPT"
name	string	Account name/description.	"Business Checking Account"
number	string	Account number.	"123456789"
type	string	Account type.	"CHECKING"
createdAt	string	Creation timestamp.	"2024-01-15T10:30:00Z"
updatedAt	string	Last update timestamp.	"2024-05-20T14:45:00Z"

2. Bank Object (Traditional Banking)

Field	Type	Description	Example
bank.name	string	Bank name.	"Chase Bank"
bank.number	string	Account number.	"123456789"
bank.routingNumber	string	Routing number (US).	"021000021"

Bank Address Object

Field	Type	Description	Example
bank.address.addressLine1	string	Primary address.	"456 Bank Street"
bank.address.addressLine2	string	Suite/floor.	"Floor 15"
bank.address.addressLine3	string	Additional info.	"Main Office"
bank.address.city	string	City.	"New York"
bank.address.stateIso	string	State code.	"NY"
bank.address.countryIso	string	Country code.	"US"
bank.address.postalCode	string	Postal code.	"10002"
bank.address.unitNumber	string	Unit number.	"1501"

3. Crypto Object (Cryptocurrency)

Field	Type	Description	Example
crypto.address	string	Crypto wallet address.	"0x742d35Cc6634C0532925a3b8D6B3985f8e091be1"

Crypto Additional Information

Field	Type	Description	Allowed Values	Example
crypto.additionalInformation.walletType	string	Type of wallet.	CPW_INSTITUTION, CPW_OTHER, CPW_UNKNOWN	"CPW_INSTITUTION"
crypto.additionalInformation.type	string	Account type.	TYPE_CRYPTO	"TYPE_CRYPTO"
crypto.additionalInformation.supportedRails	array	Supported payment methods.	CRYPTO, NFT	["CRYPTO"]

4. Fiat Object (Detailed Banking)

Field	Type	Description	Example
fiat.number	string	Account number.	"987654321"
fiat.ifsc	string	IFSC code (India).	"SBIN0000001"
fiat.swift	string	SWIFT/BIC code.	"CHASUS33"
fiat.sortCode	string	Sort code (UK).	"40-30-20"
fiat.name	string	Account name.	"Business Account"
fiat.transitNumber	string	Transit number (Canada).	"12345"
fiat.routingNumber	string	Routing number (US).	"021000021"

Fiat Additional Information

Field	Type	Description	Allowed Values	Example
fiat.additionalInformation.type	string	Regional account type.	TYPE_FIAT_US, TYPE_FIAT_GB, etc.	"TYPE_FIAT_US"
fiat.additionalInformation.supportedRails	array	Supported payment rails.	ACH, FEDWIRE, SWIFT, etc.	["ACH", "FEDWIRE"]
fiat.additionalInformation.accountType	string	Account type.	CHECKING, SAVING	"CHECKING"

Intermediary Bank (for International Transfers)

Field	Type	Description	Example
fiat.additionalInformation.intermediary.bank.name	string	Intermediary bank name.	"Citibank N.A."
fiat.additionalInformation.intermediary.bank.number	string	Intermediary account.	"876543210"
fiat.additionalInformation.intermediary.bank.routingNumber	string	Intermediary routing.	"021000089"

5. Counterparty Object

Field	Type	Description	Example
counterparty.id	string	Counterparty ID.	"cp_67890"
counterparty.name	string	Counterparty name.	"Tech Supplies Corp"
counterparty.phone	string	Counterparty phone.	"[phone]"
counterparty.email	string	Counterparty email.	"[email protected]"

6. Customer Object

Field	Type	Description	Example
customer.id	string	Customer ID.	"cust_12345"
customer.name	string	Customer name.	"John Doe"
customer.phone	string	Customer phone.	"[phone]"
customer.email	string	Customer email.	"[email protected]"
customer.status	string	Customer status.	"ACCEPT"

Field Details

Account Status Values

Status	Description
NEW	Account newly created, pending verification
AWAIT	Awaiting additional information/documentation
MODERATION	Under review by compliance team
ACCEPT	Approved and active for transactions
REJECT	Rejected during verification
BANNED	Permanently blocked from transactions
VERIFICATION	In verification process

Supported Fiat Types

TYPE_FIAT_GB	United Kingdom	UK banking system
TYPE_FIAT_EU	European Union	SEPA region
TYPE_FIAT_IN	India	Indian banking system
TYPE_FIAT_CA	Canada	Canadian banking
TYPE_FIAT_SG	Singapore	Singapore banking
TYPE_FIAT_HK	Hong Kong	Hong Kong banking
TYPE_CRYPTO	Global	Cryptocurrency network
TYPE_FIAT_BS	Bahamas	Bahamian banking system
TYPE_FIAT_PA	Panama	Panamanian banking system
TYPE_FIAT_MY	Malaysia	Malaysian banking system
TYPE_FIAT_JP	Japan	Japanese banking system
TYPE_FIAT_CN	China	Chinese banking system
TYPE_FIAT_BR	Brazil	Brazilian banking system
TYPE_FIAT_AE	United Arab Emirates	UAE banking system
TYPE_FIAT_CH	Switzerland	Swiss banking system
TYPE_FIAT_SA	Saudi Arabia	Saudi banking system
TYPE_FIAT_GT	Guatemala	Guatemalan banking system
TYPE_FIAT_QA	Qatar	Qatari banking system
TYPE_FIAT_BH	Bahrain	Bahraini banking system
TYPE_FIAT_CR	Costa Rica	Costa Rican banking system
TYPE_FIAT_TR	Turkey	Turkish banking system
TYPE_FIAT_GL	Greenland	Greenlandic banking system
TYPE_FIAT_PL	Poland	Polish banking system
TYPE_FIAT_MX	Mexico	Mexican banking system

Supported Payment Rails

Rail	Description	Region
ACH	Automated Clearing House	US
FEDWIRE	Federal Wire Transfer	US
SWIFT	International wire transfers	Global
SEPA_CT	SEPA Credit Transfer	EU
CRYPTO	Cryptocurrency transfers	Global

---

Sender Data Availability by Payment Rail

Sender/originator data completeness depends on what the sending bank and the rail itself transmit at the time the payment is initiated. Each rail has its own message format, and these formats differ in which fields are mandatory versus optional. Delos passes through and displays the data exactly as received from the sending bank/rail — nothing is withheld or lost during processing.

Rail	Sender Name	Account No. / IBAN	BIC/SWIFT	Routing/Sort Code	Sender Bank Name	Bank Address
SWIFT	Guaranteed	Guaranteed	Best-effort	n/a	Best-effort	Best-effort
SEPA_CT	Guaranteed	Guaranteed (IBAN)	Best-effort	n/a	Best-effort	Best-effort
UAEFTS	Guaranteed	Guaranteed (IBAN)	Best-effort	n/a	Best-effort	Best-effort
FPS	Guaranteed	Guaranteed	Best-effort	Best-effort	Best-effort	Best-effort
FEDWIRE	Guaranteed	Guaranteed	Best-effort	Guaranteed (routing no.)	Guaranteed (intermediary)	Best-effort
CRYPTO	n/a¹	Guaranteed (wallet address)	n/a	n/a	n/a	n/a

¹ For crypto rails, there is no banking relationship involved, so there is no equivalent of a legal sender name. The "name" field is a fixed {currency} Sender label rather than actual sender data; the wallet address is the only reliable identifier.

Guaranteed vs. best-effort, by rail:

• Guaranteed across all fiat rails: sender name (account_name) and account number/IBAN.
• Best-effort, and varies depending on the sending bank and rail: BIC, sender bank name, bank address. These fields are frequently not populated by the sending bank itself, particularly on SEPA, UAEFTS, and FPS.
• Fedwire is the exception — it consistently includes a routing number and a separately identified sender bank. This is a feature of how the Fedwire message format is structured, not something present on other rails.
• Crypto works fundamentally differently: there's no banking relationship involved at all, so the only reliable identifier is the sender's wallet address.

What determines whether the data is present:

• This depends on what the sending bank and the rail itself transmit at the time the payment is initiated. Fields like BIC or bank address are often optional in the message specification itself, so whether they're populated depends entirely on the sending bank's own practices.
• We pass through and display the data exactly as we receive it from the sending bank/rail, so what you see reflects what was actually transmitted to us.

Notes

• Account Verification: Status indicates current verification state
• Multi-format Support: Accounts can have traditional bank, fiat, and/or crypto details
• International Transfers: Intermediary bank information required for certain cross-border payments
• Compliance: All accounts undergo verification based on regional regulations
• Payment Rails: Supported rails determine available transfer methods

Common Use Cases:

• Payment processing setup and verification
• Compliance and audit reporting
• Customer relationship management
• Multi-currency account management

Examples

Real request

Authorization: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOjE2NCwiZXhwIjoxNzYxNzI5MTkzLCJrZXkiOiI1Y2ZiOGZjN2RmYjk4ZjVkYmIyZTgwNTVkZWFhN2U2Zjk4MzEyYmE3Iiwib3RwX3ZlcmlmaWVkIjpmYWxzZX0.kvjGbh4yRxE8qrD79710RiAM2spjqeSv6v0pJ9Pr7VY
accountId*: UDHW6vxOePli

Real response

{
  "item": {
    "accountId": "UDHW6vxOePli",
    "currencyCode": "USD",
    "status": "ACCEPT",
    "bank": {
      "name": "Test Eugen USD",
      "number": "Test Eugen USD",
      "address": {
        "addressLine1": "Test Eugen USD",
        "addressLine2": "",
        "addressLine3": "",
        "city": "Test Eugen USD",
        "stateIso": "Test Eugen USD",
        "countryIso": "Test Eugen USD",
        "postalCode": "Test Eugen USD",
        "unitNumber": "Test Eugen USD"
      }
    },
    "name": "Test Eugen USD",
    "number": "Test Eugen USD",
    "type": "Fiat",
    "fiat": {
      "number": "Test Eugen USD",
      "ifsc": "1234",
      "swift": "Test Eugen USD",
      "sortCode": "",
      "name": "Test Eugen USD",
      "transitNumber": "Test Eugen USD",
      "routingNumber": "Test Eugen USD",
      "additionalInformation": {
        "type": "TYPE_FIAT",
        "supportedRails": [
          "SWIFT"
        ],
        "accountType": "CHECKING"
      },
      "accountNumberType": "ANT_NOTSET",
      "transitNumberCode": "TNC_NOTSET"
    },
    "counterparty": {
      "id": "DkCSHAN-B9nW-HoakBCwCq36I",
      "name": "Test Eugen USD",
      "phone": "111",
      "email": "Test Eugen USD"
    },
    "customer": {
      "id": "Dnewcvn-euuI-vG0FZCRDjLXS",
      "name": "Test Eugen Test Eugen",
      "phone": "",
      "email": "",
      "status": "ACCEPT"
    },
    "createdAt": null,
    "updatedAt": null
  }
}