Welcome to the official reference documentation for Synctera APIs. Our APIs are the best way to automate your company's banking needs and are designed to be easy to understand and implement.
We're continuously growing this library and what you see here is just the start, but if you need something specific or have a question, contact us.
license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html title: Synctera API version: v2 servers: - description: Production url: https://api.synctera.com/v2 - description: Sandbox (no real world financial impact) url: https://api-sandbox.synctera.com/v2 security: - bearerAuth: [] tags: - description: Create and manage wire transfers name: Wires - description: Simulate receiving Wire transactions and returns name: Wire Transaction Simulations - description: >- Create and manage same currency and multi-currency international wire transfers name: International Wires (alpha) - description: Create and manage payments name: ACH - description: Simulate receiving ACH transactions and returns name: ACH Transaction Simulations - description: Configure vendor secrets for egress requests name: Egress Gateway Vendor Secret CRUD API - description: Configure webhook secrets for egress requests name: Egress Gateway Webhook Secret CRUD API - description: Create and manage documents. name: Documents - description: Create and manage EFT Canada transfers name: EFT Canada (Beta) - description: Create and manage sweep configurations name: Configs - description: Request to create and manage edd name: Trust - description: Requests to calculate and manage CRR name: CRR - description: Requests to issue and manage cards name: Cards - description: Push and pull from cards name: External Cards - description: Bulk card issuance name: Bulk Issuance - description: Requests to generate simulated transactions name: Card Transaction Simulations - description: Requests to generate simulated webhooks name: Card Webhook Simulations - description: Requests to create and manage card disputes name: Card Disputes - description: Requests to simulate card payments name: Card Simulations - description: Create and manage accounts name: Accounts - description: Create and manage transactions name: Transactions (beta) - description: Create and manage spending controls name: Spend Controls (beta) - description: | Requests to create and manage fees name: Fees (beta) - description: | Requests to create and manage Rewards name: Rewards (beta) - description: Create and manage disputes name: Disputes - description: Create and manage tenant-level transaction limits name: Tenant Limits (beta) - description: | Requests to create and manage batch payments name: Batch Payments (alpha) - description: Manage negative balance processes name: Negative Balance - description: | Manage fee products and fee configs for automated fee collection name: Fee Products - description: | Manage reward products and reward configs for automated cashback rewards name: Reward Products - description: Create and manage holds name: Hold - description: Create and manage transactions name: Transactions - description: Create and manage transactions name: Transactions (internal) - description: Create and manage scheduled transactions name: Scheduled Transactions (internal) - description: Create and manage spending controls name: Spend Controls - description: Create and manage tenant configurations name: Tenant Configs - description: Lookup merchant information name: Merchants - description: See balance history name: BalanceHistory - description: API for effective balances name: effective_balances - description: Transaction lines API name: transactions - description: Requests for risk evaluation and decisioning name: Risk Evaluations - description: Requests for transaction risk detection name: Transaction risk - description: Configuration and management of transaction monitoring rules name: Transaction Monitoring - description: Request to create and manage deposits using remote deposit capture name: Remote Check Deposit - description: Request to create and manage rdc configurations name: RDC Config - description: Apple Pay APIs name: Apple Pay - description: Requests to create and manage webhooks name: Webhooks - description: Requests to generate simulated transactions name: Cash Transaction Simulations (alpha) - description: >- Testing endpoints to simulate in-store cash deposits. Available in sandbox environments only. name: In-Store Cash Deposit Simulations - description: Create and manage barcodes for in-store cash deposits name: In-Store Cash Deposits - description: Create and manage Cash Order and Cash Deposit transfers name: Cash Orders and Deposits (alpha) - description: FDX authentication and data transfer using Plaid Core Exchange name: Plaid Core Exchange (beta) - description: Request to create and manage payment_schedules name: Cronut - description: Request to create and manage statements name: Statements - description: Create and manage Synctera Pay templates name: SyncteraPay - description: Account Template name: Account Templates - description: >- Account programs define configurations for payment rails and transaction capabilities across different account types. name: Account Programs - description: Requests to create and manage account products, including fees, interest. name: Account Products - description: | The internal account resource is used for managing links to internal accounts where the funds are managed by integrators. name: Internal Accounts - description: Requests to create and manage API keys name: API Keys - description: Requests to manage banks name: Banks - description: Requests to create and manage customers name: Customers - description: > A natural person (individual human) that is relevant to the Synctera platform in some way: e.g. a personal customer or a director/officer/owner of a business. name: Persons - description: > A legal entity (corporation, partnership, etc.) that is relevant to the Synctera platform in some way: a business customer or some other organization that has an ownership share in such a business customer. name: Businesses - description: > The fintech profile document resource is used to track the approval status of any documents which must be reviewed by a bank. This includes regulatory documents which will be presented to the fintech's end users, and also any documents that help the bank understand the fintech's fitness for duty. name: Fintech Profile - description: | The disclosures resource is used to track the status of disclosures and ensure that all parties have been shown the necessary disclosures to meet regulatory obligations. name: Disclosures - description: | The Disclosures resource is used to track the status of disclosures and ensure that customers have been shown the necessary disclosures to meet regulatory obligations. name: Disclosures (deprecated) - description: | The External Account resource is used for managing links to accounts that operate outside of the Synctera ecosystem. name: External Accounts - description: History name: History - description: Requests to initiate customer verification. name: KYC Verification (deprecated) - description: Requests to initiate customer verification. name: KYC/KYB Verifications - description: Requests to screen parties against sanctions watchlists name: Sanctions Screening - description: Requests to manage monitoring subscriptions and alerts for customers. name: Monitoring - description: Requests to manage partners name: Partners - description: Request to create and manage party groups and party group members name: Party Groups - description: Requests to create and manage roles name: Roles - description: > Represents the relationships between parties. A relationship can exist between personal customers, business customers, or non-customer persons/organizations. name: Relationships - description: Request to create and manage users name: Users - description: Request to enroll, renew, or cancel watchlist monitors name: Watchlist (deprecated) - description: Retrieve user identity information name: Identity - description: Endpoints for modifying or fetching posting dates name: Posting Dates - description: Admin API for Middesk configuration using the tenants API keys. name: Middesk - description: Requests to search and manage compliance searches name: Compliance Searches - description: Requests to configure vendors. name: Vendor Configurations - description: Requests to create and manage notes name: Notes - description: > Represents the compliance rules that are used to verify certain kinds of money movement. name: Compliance Rules - description: Requests to create licenses name: Licenses - description: >- Used to configure bank accounts for which synctera accounts are considered a "subledger" to name: Bank Account - description: Requests to search financial institutions name: Institutions (Beta) - description: Requests to manage addresses name: Addresses - description: Requests to Admins to grant permissions to user name: Request Permissions - description: Manage contacts for bank and fintech partners name: Contacts - description: Requests to create and manage personal ID configurations name: Personal ID Configuration - description: >- Migration mappings associate resources from an old tenant identity with a new tenant identity. name: Migration Mappings - description: Create a credit application. name: Applications (beta) - description: Billing period summaries name: Billing Period Summaries - description: Customer Service Details for disputes and billing inquiries name: Customer Service Details - description: Billing rates name: Billing Rates - description: Rates name: Rates - description: Lending Config name: Lending Config - description: Manage credit disputes name: Credit Disputes - description: Payments related to lending accounts name: Payments - description: Tenant Config name: Tenant Config - description: Bank Delinquency Configuration name: Bank Delinquency Configuration - description: >- Per bank/partner account-type mapping to FFIEC collateral codes used for regulatory call report furnishment. name: Collateral Code Configuration - description: >- Rules that map a posted payment transaction (bank/partner + transaction attributes) to a regulatory payment code. NULL match columns act as wildcards. name: Payment Code Configuration - description: Autopay configuration management for lending accounts name: Autopay Configs - description: Autopay payment records for billing periods name: Autopays - description: Configuration for mapping LoanPro events to Payola transaction parameters name: LoanPro Transaction Event Config - description: >- Aggregated write-off amounts for lending accounts, computed from posted transactions. name: Write Off Amounts paths: /statements/{statement_id}: summary: Statements get: tags: - Statements summary: Get a statement description: | Gets a full statement by its ID. operationId: getStatement parameters: - $ref: '#/components/parameters/statement_id' responses: '200': content: application/json: schema: $ref: '#/components/schemas/statement' description: statement '401': $ref: '#/components/responses/unauthorized' '403': $ref: '#/components/responses/forbidden' '404': $ref: '#/components/responses/not_found' '500': $ref: '#/components/responses/internal_server_error' components: parameters: statement_id: description: The unique identifier of a statement in: path name: statement_id required: true schema: example: 7d943c51-e4ff-4e57-9558-08cab6b963c7 format: uuid type: string schemas: statement: discriminator: mapping: CHARGE_SECURED: $ref: '#/components/schemas/charge_secured_statement' CHARGE_UNSECURED: $ref: '#/components/schemas/charge_unsecured_statement' CREDIT_CARD: $ref: '#/components/schemas/credit_card_statement' DEPOSIT: $ref: '#/components/schemas/depository_statement' LINE_OF_CREDIT: $ref: '#/components/schemas/line_of_credit_statement' propertyName: statement_type oneOf: - $ref: '#/components/schemas/depository_statement' - $ref: '#/components/schemas/line_of_credit_statement' - $ref: '#/components/schemas/charge_secured_statement' - $ref: '#/components/schemas/charge_unsecured_statement' - $ref: '#/components/schemas/credit_card_statement' title: Statement charge_secured_statement: allOf: - $ref: '#/components/schemas/base_statement' - properties: credit_summary: $ref: '#/components/schemas/credit_summary' security_account_summary: $ref: '#/components/schemas/security_account_summary' required: - security_account_summary - credit_summary type: object description: A statement for a charge secured account title: Charge Secured Statement charge_unsecured_statement: allOf: - $ref: '#/components/schemas/base_statement' - properties: credit_summary: $ref: '#/components/schemas/credit_summary' required: - credit_summary type: object description: A statement for a charge unsecured account title: Charge Unsecured Statement credit_card_statement: allOf: - $ref: '#/components/schemas/base_statement' - properties: credit_summary: $ref: '#/components/schemas/credit_summary' required: - credit_summary type: object description: A statement for a credit card account title: Credit Card Statement depository_statement: allOf: - $ref: '#/components/schemas/base_statement' - properties: saving_summary: $ref: '#/components/schemas/saving_summary' required: - saving_summary type: object description: A statement for a depository account title: Depository Statement line_of_credit_statement: allOf: - $ref: '#/components/schemas/base_statement' - properties: credit_summary: $ref: '#/components/schemas/credit_summary' required: - credit_summary type: object description: A statement for a line of credit account title: Line of Credit Statement error: description: Synctera error responses in API v1 implement a custom error schema. properties: code: description: > A machine-readable string that identifies the error for programmatic use. example: BAD_REQUEST_BODY type: string detail: description: | A human-readable string explaining this particular error. example: 'Missing required fields: first_name, dob' type: string status: description: HTTP status code for this response example: 400 type: integer title: Synctera error response type: object base_statement: allOf: - $ref: '#/components/schemas/statement_summary' - properties: account_summary: $ref: '#/components/schemas/account_summary' authorized_signers: items: $ref: '#/components/schemas/person' readOnly: true type: array closing_balance: description: >- The account balance at the end of the statement period, in ISO 4217 minor currency units. format: int64 type: integer customer_service_details: $ref: '#/components/schemas/customer_service_details' disclosure: type: string exclude_jit_transactions: default: false description: Ignore "JIT funding" transactions when generating a statement example: false type: boolean include_child_transactions: default: false description: >- Include transactions from sub-accounts when generating a statement example: false type: boolean joint_account_holders: items: $ref: '#/components/schemas/person' readOnly: true type: array opening_balance: description: >- The account balance at the start of the statement period, in ISO 4217 minor currency units. format: int64 type: integer pdf_document_id: description: The ID of the uploaded PDF document in docstore format: uuid readOnly: true type: string primary_account_holder_business: $ref: '#/components/schemas/business' primary_account_holder_personal: $ref: '#/components/schemas/person' statement_type: $ref: '#/components/schemas/statement_type' total_transactions: description: | The total number of transactions for this statement period. format: int64 type: integer required: - statement_type - include_child_transactions - exclude_jit_transactions type: object type: object credit_summary: description: >- A summary of the accrued interest for the credit account in the current period. properties: amount_over_limit: description: >- The portion of the posted account balance that exceeds the account's credit limit, in ISO 4217 minor currency units. example: 100000 format: int64 type: integer amount_past_due: description: > Any outstanding balance from a previous statement for this account in ISO 4217 minor currency units. example: 100000 format: int64 type: integer apr: description: The annual percentage rate of the credit account, in basis points. format: int64 type: integer balance_for_interest: description: >- Balance on which interest is computed during the time interval covered by the statement. format: int64 type: integer credit_limit: description: >- The credit limit of the credit account, in ISO 4217 minor currency units. Not applicable for charge secured accounts. format: int64 type: integer cumulative_lifetime_writeoff: description: > Lifetime posted write-off amount for the account in ISO 4217 minor currency units, net of any write-off reversals. Captured as a snapshot at statement generation time; future write-offs will not retroactively update historic statements. Omitted when the account has never had a write-off recorded. example: 25000 format: int64 type: integer disclosure: description: A suggested regulatory disclosure to display on the statement. example: >- We have told the credit bureau(s) about a late payment, missed payment or other default on your account. This information may be reflected in your credit report. type: string disputed_balance: description: >- The disputed balance on the credit account in ISO 4217 minor currency units. format: int64 type: integer fees: description: >- The total fees charged on the credit account in ISO 4217 minor currency units during the time interval covered by the statement. format: int64 type: integer fees_ytd: description: >- The total fees charged on the credit account in ISO 4217 minor currency units for the year to date. format: int64 type: integer interest: description: >- The total interest charged on the credit account in ISO 4217 minor currency units during the time interval covered by the statement. format: int64 type: integer interest_ytd: description: >- The total interest charged on the credit account in ISO 4217 minor currency units for the year to date. format: int64 type: integer is_past_due: description: Whether or not the credit account is past due on payment. type: boolean last_payment_date: description: The date of the last payment received. format: date type: string minimum_payment_due: description: >- The minimum payment amount due by the payment due date in ISO 4217 minor currency units. format: int64 type: integer payment_due: description: >- The total amount due by the payment due date in ISO 4217 minor currency units. format: int64 type: integer payment_due_date: description: The date the next payment is due. format: date type: string payments_received: description: The sum of all payments received in ISO 4217 minor currency units. format: int64 type: integer title: Credit Summary type: object security_account_summary: description: A summary for the security account backing the credit account. properties: account_id: description: The unique identifier of the backing account. format: uuid type: string account_number: description: Account number of the backing account. type: string account_type: description: | The type of the account. It refers to the backing account. type: string apy: description: > The annual percentage yield (APY) for the security account for this statement period, in basis points. For example, an APY of 5.5% will display as 550. example: 550 format: int64 type: integer closing_balance: description: >- The security account balance at the end of the statement period, in ISO 4217 minor currency units. For example, $1,000 USD will be displayed as 100000. example: 100000 format: int64 type: integer disclosure: type: string interest: description: > The total interest earned by the security account for this statement period in ISO 4217 minor currency units. For example, $1.50 USD of interest will be displayed as 150. example: 150 format: int64 type: integer interest_previous_month: description: > The total interest earned by the security account in the previous statement period in ISO 4217 minor currency units. For example, $1.50 USD of interest will be displayed as 150. example: 150 format: int64 type: integer interest_previous_year: description: > The total interest earned by the security account in the previous year in ISO 4217 minor currency units. For example, $100 USD of interest will be displayed as 10000. example: 10000 format: int64 type: integer interest_ytd: description: > The total interest earned by the security account for this year to date in ISO 4217 minor currency units. For example, $100 USD of interest will be displayed as 10000. example: 10000 format: int64 type: integer opening_balance: description: >- The security account balance at the start of the statement period, in ISO 4217 minor currency units. For example, $1,000 USD will be displayed as 100000. example: 100000 format: int64 type: integer title: Security Account Summary type: object saving_summary: description: >- A summary of the accrued interest for the saving account in the current period properties: accrual_days: description: > The number of days for which interest was accrued. In most cases this will match the number of days in the billing period, but may be less if an account was closed part way through the period. format: int32 type: integer apy: description: > The annual percentage yield (APY) for this statement period, in basis points. For example, an APY of 5.5% will display as 550. example: 550 type: integer interest_earned: description: > The total interest earned by the depository account for this statement period in ISO 4217 minor currency units. For example, $1.50 USD of interest will be displayed as 150. example: 150 format: int64 type: integer interest_earned_previous_month: description: > The total interest earned by the depository account in the previous statement period in ISO 4217 minor currency units. For example, $1.50 USD of interest will be displayed as 150. example: 150 format: int64 type: integer interest_earned_previous_year: description: > The total interest earned by the depository account in the previous year in ISO 4217 minor currency units. For example, $100 USD of interest will be displayed as 10000. example: 10000 format: int64 type: integer interest_earned_ytd: description: > The total interest earned by the depository account for this year to date in ISO 4217 minor currency units. For example, $100 USD of interest will be displayed as 10000. example: 10000 format: int64 type: integer title: Saving Summary type: object statement_summary: properties: account_id: description: The unique identifier of the account the statement belongs to format: uuid readOnly: true type: string billing_period_id: description: The billing period this statement corresponds to format: uuid readOnly: true type: string credit_summary: $ref: '#/components/schemas/credit_summary' end_date: description: >- The date indicating the ending of the time interval covered by the statement format: date readOnly: true type: string id: description: statement ID format: uuid readOnly: true type: string issue_date: description: The date when the statement has been issued format: date readOnly: true type: string saving_summary: $ref: '#/components/schemas/saving_summary' security_account_summary: $ref: '#/components/schemas/security_account_summary' start_date: description: >- The date indicating the beginning of the time interval covered by the statement format: date readOnly: true type: string statement_type: $ref: '#/components/schemas/statement_type' title: Statement type: object account_summary: properties: account_number: description: Account number type: string account_status: description: Account Status type: string account_type: description: The type of the account. type: string balance_ceiling: properties: balance: description: >- Maximum balance in the account's currency. Unit in ISO 4217 minor currency units. format: int64 type: integer type: object balance_floor: properties: balance: description: >- Minimum balance in the account's currency. Unit in ISO 4217 minor currency units. format: int64 type: integer type: object creation_time: description: Account creation time format: date-time type: string currency: description: >- Account currency or account settlement currency. ISO 4217 alphabetic currency code. Default USD example: USD pattern: ^[A-Z]{3}$ type: string customer_type: description: Customer type type: string financial_institution: $ref: '#/components/schemas/financial_institution' id: description: The unique identifier of the account the statement belongs to format: uuid type: string last_updated_time: description: Account last modification time format: date-time type: string nickname: description: User provided account nickname type: string title: Account Summary type: object person: properties: creation_time: format: date-time type: string first_name: type: string id: format: uuid type: string last_name: type: string last_updated_time: format: date-time type: string middle_name: type: string relationship_type: type: string title: Person type: object customer_service_details: description: >- The customer service details of the fintech partner, e.g. phone number, email address, etc. properties: address: $ref: '#/components/schemas/address' email: description: The customer service email address type: string phone_number: description: The customer service phone number type: string title: Customer Service Details type: object business: allOf: - required: - status - is_customer - $ref: '#/components/schemas/base' description: Represents a business customer. type: object statement_type: description: The type of statement enum: - DEPOSIT - LINE_OF_CREDIT - CHARGE_SECURED - CHARGE_UNSECURED - CREDIT_CARD title: Statement Type type: string x-enumDescriptions: CHARGE_SECURED: Secured charge card account statement (e.g. for Smart Charge Cards) CHARGE_UNSECURED: Unsecured charge card account statement (e.g. for Smart Charge Cards) CREDIT_CARD: Credit card account statement DEPOSIT: Deposit account statement (e.g. for CHECKING or SAVING accounts) LINE_OF_CREDIT: Line of Credit account statement financial_institution: properties: legal_address: $ref: '#/components/schemas/address' name: type: string phone_number: type: string title: Financial Institution type: object address: properties: address_line_1: description: Street address line 1 example: 100 Main St. type: string address_line_2: description: Street address line 2 example: Suite 99 type: string address_type: description: | Specifies the address type. enum: - BILLING - LEGAL - SHIPPING - OPERATING - OTHER example: SHIPPING readOnly: true type: string city: description: City example: New York type: string country_code: description: ISO-3166-1 Alpha-2 country code example: US pattern: ^[A-Z]{2}$ type: string id: $ref: '#/components/schemas/id' is_registered_agent: description: >- Indicates whether an address is a registered agent. Omitted if the address is not a registered agent. example: true type: boolean nickname: description: > A nickname for the address. This is used to identify the address in the UI. example: Home type: string postal_code: description: > Postal code. For US, formats of 12345 or 12345-1234 are accepted. For CA, formats of A1A 1A1 or A1A1A1 (regardless of case) are accepted, and will be converted to A1A 1A1 format. example: '28620' type: string state: description: > State, region, province, or prefecture. This is the ISO-3166-2 subdivision code, excluding the country prefix. For example, TX for Texas USA or TAM for Tamaulipas Mexico. Its length varies by country, e.g. 2 characters for US, 3 for MX. example: NY type: string required: - address_line_1 - country_code type: object base: properties: addresses: description: All of the customer's addresses items: $ref: '#/components/schemas/address' readOnly: true type: array classifications: $ref: '#/components/schemas/classifications' compliance_restrictions: description: > The types of compliance that the business needs to adhere to * `LICENSED_CANNABIS` – A type of compliance restriction where the business would need a cannabis license in order to operate. items: enum: - LICENSED_CANNABIS type: string type: array creation_time: description: The date and time the resource was created. example: '2010-05-06T12:23:34.321Z' format: date-time readOnly: true type: string customer_active: description: The date and time this business became a bank customer. example: '2010-05-06T12:23:34.321Z' format: date-time readOnly: true type: string ein: description: >- U.S. Employer Identification Number (EIN) for this business, in the format xx-xxxxxxx. example: 12-3456789 type: string email: description: Business's email. example: alice@example.com type: string entity_name: description: Business's legal name. example: Apex Corporation type: string formation_date: description: >- Date the business was legally registered in RFC 3339 full-date format (YYYY-MM-DD). example: '2000-01-01' format: date type: string formation_state: description: >- U.S. state where the business is legally registered (2-letter abbreviation). example: NY type: string has_accounts: $ref: '#/components/schemas/has_accounts' id: description: Business's unique identifier. example: 7d943c51-e4ff-4e57-9558-08cab6b963c7 format: uuid readOnly: true type: string is_customer: $ref: '#/components/schemas/is_customer' last_updated_time: description: The date and time the resource was last updated. example: '2010-05-06T12:23:34.321Z' format: date-time readOnly: true type: string legal_address: $ref: '#/components/schemas/legal_address' metadata: $ref: '#/components/schemas/metadata' phone_number: description: >- Business's phone number with country code in E.164 format. Must have a valid country code. Area code and local phone number are not validated. example: '+14374570680' pattern: ^\+[1-9]\d{1,14}$ type: string spend_control_ids: $ref: '#/components/schemas/spend_control_ids3' status: description: > Status of the business. One of the following: * `PROSPECT` – a potential customer, used for information-gathering and disclosures. * `ACTIVE` – is an integrator defined status. Integrators should set a business to active if they believe the person to be qualified for conducting business. Synctera will combine this status with other statuses such a verification to determine if the business is eligible for specific actions such as initiating transactions or issuing a card. * `FROZEN` – business's actions are blocked for security, legal, or other reasons. * `SANCTION` – business is on a sanctions list and should be carefully monitored. * `DISSOLVED` – an inactive status indicating a business entity has filed articles of dissolution or a certificate of termination to terminate its existence. * `CANCELLED` – an inactive status indicating that a business entity has filed a cancellation or has failed to file its periodic report after notice of forfeiture of its rights to do business. * `SUSPENDED` – an inactive status indicating that the business entity has lost the right to operate in it's registered jurisdiction. * `MERGED` – an inactive status indicating that the business entity has terminated existence by merging into another entity. * `INACTIVE` – an inactive status indicating that the business entity is no longer active. * `CONVERTED` – An inactive status indicating that the business entity has been converted to another type of business entity in the same jurisdiction. enum: - PROSPECT - ACTIVE - FROZEN - SANCTION - DISSOLVED - CANCELLED - SUSPENDED - MERGED - INACTIVE - CONVERTED type: string structure: description: Business's legal structure. enum: - SOLE_PROPRIETORSHIP - PARTNERSHIP - LLC - CORPORATION - S_CORPORATION - NON_PROFIT - OTHER example: CORPORATION type: string tenant: $ref: '#/components/schemas/tenant_id' trade_names: description: >- All registered 'doing business as' (DBA) or trade names for this business. example: - Apex - Apex LLC - CorporationID#77231 items: type: string type: array verification_last_run: description: Date and time KYB verification was last run on the business. example: '2010-05-06T12:23:34.321Z' format: date-time readOnly: true type: string verification_status: $ref: '#/components/schemas/verification_status' website: description: Business's website. example: https://example.com type: string type: object id: description: The unique identifier for this resource. example: 7d943c51-e4ff-4e57-9558-08cab6b963c7 format: uuid readOnly: true type: string classifications: description: > Specifies the classification of a party for banks. This may contain multiple values for a combined classifications list of customers. items: $ref: '#/components/schemas/classification' readOnly: true type: array has_accounts: description: This flag indicates whether the person or business has accounts. readOnly: true type: boolean is_customer: description: > True for personal and business customers with a direct relationship with the fintech or bank. Set this to true for any customer related to an account. example: true type: boolean legal_address: allOf: - description: Legal address - $ref: '#/components/schemas/address' metadata: description: > Optional field to store additional information about the resource. Intended to be used by the integrator to store non-sensitive data. type: object spend_control_ids3: description: List of spend control IDs to control spending for the customer items: example: 7d943c51-e4ff-4e57-9558-08cab6b963c7 format: uuid type: string maxItems: 100 type: array tenant_id: description: | The id of the tenant containing the resource. example: abcdef_ghijkl type: string verification_status: description: > The result of a KYC/KYB verification. One of the following: * `UNVERIFIED` – verification has not been completed for this customer. * `PENDING` – verification is in progress for this customer. * `PROVISIONAL` – partially verified or verified with restrictions. * `ACCEPTED` – the customer has been verified. * `REVIEW` – verification has run and issues have been identified and require review. * `REJECTED` – the customer was rejected and should not be allowed to take certain actions e.g., open an account. enum: - UNVERIFIED - PENDING - PROVISIONAL - ACCEPTED - REVIEW - REJECTED example: ACCEPTED readOnly: true type: string classification: description: | Specifies the classification of a party. enum: - BANK_CUSTOMER - AUTHORIZED_USER - PROSPECT - INACTIVE_BANK_CUSTOMER type: string responses: unauthorized: content: application/json: schema: $ref: '#/components/schemas/error' description: Unauthorized forbidden: content: application/json: schema: $ref: '#/components/schemas/error' description: Forbidden not_found: content: application/json: schema: $ref: '#/components/schemas/error' description: Resource not found internal_server_error: content: application/json: schema: $ref: '#/components/schemas/error' description: Internal server error securitySchemes: bearerAuth: bearerFormat: api_key scheme: bearer type: http ````