• Business Identification Number API: Added new endpoints to support the German Economic Identification Number (WIdNr) for business onboarding: * POST /v1/businesses/{business_id}/business_identification_numbers to submit a BIN. * GET /v1/businesses/{business_id}/business_identification_numbers/{id} to retrieve a BIN. * PATCH /v1/businesses/{business_id}/business_identification_numbers/{id} to update a BIN. (For full details, see the Business Identification Number API Reference).

Updated

• Onboard a Business Guide:
  • Updated the onboarding flow and diagram to include the Business Identification number as a required step.
  • Add a new requirement to include business annual turnover when collecting business data.
• BKYC Guide
  • Updated the onboarding flow and diagram to include the Business Identification number as a required step.

• Savings accounts API reference: Introduced new endpoints and fields to manage the association between a person's savings account and their primary transaction account.
  • New Field:interest_tier: Added to the mapping resource to allow for Partner-managed interest rate categorization.
  • GET Retrieve a savings account mapping: Returns current mapping details, including the assigned interest_tier and associated account.
  • PATCH Update a savings account mapping: Allows you to transition the main account association or adjust the interest_tier.
  • API Reference: Savings accounts new endpoints.

Updated

• Savings accounts guide:
  • Managing Mappings: Updated the guide to include operational instructions for GET and PATCH methods.
  • Tiered Interest Logic: Added a requirement to provide the interest_tier value when multiple standard rates are configured; otherwise, the account defaults to the base tier.
  • Prerequisites: Noted that these endpoints are available for Person accounts only and require an initial mapping via the POST method.
  • Documentation: Savings Accounts Guide.

• FATCA self-declaration (Retail & Business): Updated the mandatory legal wording for all onboarding compliance screens to align with the latest regulatory policy.

  • Residency threshold: Updated the "Substantial Presence Test" criteria to 183 days (previously 180 days) to ensure regulatory precision.
  • Partner placeholders: Introduced flexible placeholders (e.g., [the Bank/us/Solaris]) within the legal strings. This allows you to select the term that best fits your specific business setup and customer relationship.
  • Documentation: Legal and compliance screens

• Account Closure (Reasons): New In/external closure reasons added

  • Webhook: ACCOUNT_CLOSURE_REQUEST new closure_reasons added.
  • Webhook: ACCOUNT_CLOSURE_REQUEST_UPDATE new closure_reasons added.
  • Account closure guide Types of account closures new In/external closure reasons added. (ORDINARY & IMMEDIATE)

The following decline reasons are scheduled for future activation. Solaris will provide a separate notification before these reasons become active in the production environment.

• Webhook: CARD_AUTHORIZATION_DECLINE_V2. New decline reasons added.
• The Appendix V: Transaction declined reasons (V2) New decline reasons added.

• Seizures (Timelines & Definitions): Corrected the processing logic for seizure payouts and blocks to use a calendar month instead of a fixed 4-week period.

  • Automatic Payouts (Person): Funds are now paid out to creditors after 1 month (previously calculated as 4 weeks).
  • Pre-Attachment Blocks: The provisional blocking period for PRE_ATTACHMENT seizures is now 1 month (previously 4 weeks).
  • Legal Definitions: Added specific German legal terms (e.g., Pfändungs- und Einziehungsverfügung) to the documentation to help map physical documents to API resources.
  • Documentation: Seizures Guide

• CARD_LIFECYCLE_EVENT Webhook: Reason field was added to this webhook event in order to better understand why a card was closed. CARD_LIFECYCLE_EVENT

• Close a card: Payload for request body added. Close a card

• Device Binding via Activation Code (QR): Introduced a new, secure method for binding customer devices using an Activation Code (QR). This alternative to the existing SMS OTP flow allows you to generate a code, deliver it securely (e.g., via physical mail or a secure inbox), and bind a device by scanning a QR code. This is particularly useful for use cases requiring higher security assurance or where SMS delivery is not preferred.
  • New Challenge Type: Implemented the activation_code challenge type for the /mfa/devices endpoint.
  • Management Endpoints: Added new endpoints to create, retrieve, list, and delete activation challenges.
  • Lifecycle Tracking: Added "Delivery Events" to track when an activation code is dispatched to the customer.
  • Webhooks: Added the ACTIVATION_CHALLENGE_CREATION event to notify your backend when a code is generated (e.g., by a Support Agent).
  • Documentation:
    • Device Binding Guide (Major update: new tabbed integration steps)
    • Create Activation Challenge

Updated

• Onboarding Guides: Updated the "What's next" sections in the Person and Business onboarding guides to explicitly mention the choice between SMS and QR-based device binding for Strong Customer Authentication (SCA).

  • Onboard a person
  • Onboard a business

• Data Collection (Mobile Numbers): Clarified that the "Combined Flow" (verifying a mobile number and binding a device in one step) is only available when using the SMS device binding method. Partners using the new QR flow must verify mobile numbers separately.

  • Documentation: Data Collection

• Webhooks: Updated the Available webhook events list to include the new ACTIVATION_CHALLENGE_CREATION event.

• Developer Help Center: We have launched a new Developer Help Center to assist with common integration challenges. This central hub provides:
  • Environment Reference: Verified URLs for Sandbox and Production authentication.
  • Troubleshooting Guides: Quick fixes for 401/403 errors and Webhook delivery failures.
  • Sandbox Funding: Explicit instructions on how to request funds for test accounts.
  • Support Channels: A guide on how to route tickets to the correct team (Onboarding vs. Incident Management).

Updated

• Webhooks Retry Logic: Clarified the specific timeout and retry mechanism for webhook delivery. This update replaces the previous general guidance with precise configuration details to help you better configure your server timeouts and error handling.

  • Timeout: 30 seconds
  • Retry Strategy: Exponential backoff (max 25 attempts) spanning approximately 5 days (previously documented as 7 days).
  • Documentation: Updated the Webhook notification delivery section with the exact parameters.

• Savings Account: Added rule_type and interest_profile_id parameters to the interest details endpoints for both person and business savings accounts.

  • New Parameters:
    • rule_type: Specifies the type of rule mapped to the partner (e.g., DEFAULT, PROMOTION).
    • interest_profile_id: The unique identifier (UID) of the interest profile.
  • Documentation:
    • Get interest details for a person's savings account
    • Get interest details for a business' savings account

• Data Collection (Italy): Updated the data collection requirements for customers in the Italian branch to ensure successful tax ID calculation and address validation.

  • Address & Birth Location: Added strict validation rules for city, province, and postal_code fields. Developers must now validate user input against provided official lists.
  • Foreign Birth Countries: Clarified the requirement to set birth_province to EE for customers born outside of Italy.
  • Documentation: Updated the Data Collection guide with direct download links for the required Commune, Province, and Country CSV lists.

• BankIdent Plus:

  • Account Reactivation: Added a new endpoint to reactivate an identification account after a failed BankIdent Plus identification. If a fallback identification (e.g., VideoIdent) is successful within 60 days, you can now use the reactivate endpoint to restore the account details.
  • Status Documentation: Added pre_successful and pending_account_creation to the Key Status Transitions table.
  • Enum Updates: Updated identification status enums for the Create and Retrieve Identification endpoints.

We have introduced a new Identification method called Bankident Plus, the guide for the same can be found below.

• BankIdent Plus

• Overdraft Webhooks: Introduced two new webhooks to provide real-time updates on overdraft interest rate changes. This eliminates the need to poll the GET /consumer-overdraft or GET /overdraft endpoints to check for changes to the interest_accrual_rate.

  • New Webhooks:
    • CONSUMER_OVERDRAFT_INTEREST_RATE_CHANGE
    • FREELANCER_OVERDRAFT_INTEREST_RATE_CHANGE
  • Documentation:
    • New Webhooks were added to the Consumer Overdraft guide and the Freelancer Overdraft guide detailing the implementation.

• Compliance (AML): Updated the review cycle for the AML update process in Germany. The new, shorter cycles are:

  • Low-risk customers: every 5 years (previously 7)
  • Medium-risk customers: every 3 years (previously 5)

• Device Monitoring: The Device Monitoring guide has been updated with new SDK requirements:

  • Step 1: Install SDK now lists new minimum required versions for Android (v6.8.0+), iOS (v5.6.1+), Web (v6.8.0+), and React Native (v3.3.0+).
  • Step 4: Initialize Seon SDK includes an updated initialization snippet for the Web SDK.

• Card Allowlist API: Corrected the example card_id in the Create a card allowlist response. The example now correctly uses the mcrd id instead of pcrd.

• Clarified default and maximum SEPA Instant Limits. The documentation for SEPA Instant Limits has been updated with important details about default and maximum configurable values.
  • Attempting to set a limit above the maximum will result in an API error.

• changes added to Create a Person and omboard a person guide to reflect upcomming validation for birth city

• Added SEPAInstantCreditTransfer as reservation_type for RESERVATION_CREATED and RESERVATION_RESOLVED webhook
• Updated the Vop Guide with new status VERIFICATION_NOT_SUPPORTED
  • the same was added as status in the submit a new verification of payee endpoint
• removed statement that verification_of_payee_id will be mandatory for Batch Transfers endpoint

• Updated guide for SEPA Direct Debit:
  • removed legacy endpoints for outgoing SDD
• Updated API specs for new BankIdent Plus product
  • Added bank_plus as method for Identification related endpoints
  • Added bank_plus as method for Identification webhook
  • new endpoint GET Retrieve the identification account for a person identification added
  • new webhook IDENTIFICATION_REFERENCE_TRANSFER_ATTEMPT added
• Updated status description for Sepa Credit Batch Transfers

• Link for seon web integration has been updated Step 1: Install SDK of your choice
• update guide for SEPA credit Batch transfers to include all related endpoints for this process

• Webhook TAX_EXEMPTION_UPDATED contains now a failure_reason field in case the request failed

Updated

• Business onboarding guide updates
  • updated appendix II - BKYC required documents
  • added new appendix IV - License requirements
  • added new appendix V - Business Registry offices
  • same changes are introduced here as well BKYC guide, Business Credit Cards, Business Fronting Loans, Business Fronting Factoring & Trade Finance
• Payload for webhooks DEPOSIT_ACCOUNT_UPDATED & TAX_EXEMPTION_UPDATED are updated

• Updated Guide for SEPA Credit Batch Transfers

• Webhook MESSAGE to Webhooks & Decoupled cards for consumers

• Guide for SEPA Batch Transfers

Deleted

• Missleading NOTE deleted from BKYC guied

• New section created for B2B review fields AML-update-process
• Added new Guide for Scheduled Transfers with SEPA
• Added new Webhook for status change during Scheduled Transfers

Changed

• Added section Business Customers (B2B) under AML-update-process
• Updated API specifications for Verification of Payee
• Updated API specifications for Scheduled Transfers

• Create card spending limit control (V2): Added field positive_balance_limitin the request
• Index card spending limit controls (V2): Added field positive_balance_limitin the response
• Account opening endpoints: Added SAVINGS_ACCOUNT_EXTERNAL_REFERENCE_CONSUMER_GERMANY as possible product name and SAVINGS_PERSONAL_EXTERNAL_REFERENCE as possible account type
• Autoident Guide: Added new guide for Autoident identification for re-KYC purposes
• Identification endpoints: Added new method idnow_autoident for relared person identification endpoints
• Added a new webhook event CARD_DELIVERY_TRACKING
• Batch Transfers:Added new API for Batch Transfers to comply with SEPA regulations.
• Scheduled Transfers:Added new API for Scheduled Transfers to comply with SEPA regulations.
• Sepa Instant Limits:Added new API to configure Sepa Instant Limits to comply with SEPA regulations.
• [Retrieve SEPA Credit transfers] Added a new API to retrieve SEPA Credit transfers using various filters [Now deleted]

• Add Annual Turnover : Added a new API end point to collect the Annual Turnover for Businesses.

Changed

• GET Account bookings: Updated the card related meta_info to indicate transaction_id
• Create a Person: Updated the requirement for the last_name field to indicate an empty last name with N/A
• Index accounts: Limit page size to max of 200
• Search for business's commercial registration: Added missing field commercial_registry_industry_key in the response
• Appendix III: Testing samples for GET Search for business commercial registratio: Updated testing samples

• POST Initiate a payout to a reference account: New reference payout endpoint that combines both person and business payouts.

Changed

• Safeguarding Accounts: Updated with the new reference account endpoint
• Decoupled cards for consumers: Updated with the new reference account endpoint
• Restricted accounts: Updated with the new reference account endpoint
• Document collection: Updated section about required documents for freelancers
• GET Business : Updated the field for AML follow up date for Businesses
• Initiate account closure request: Fixed mistake in the endpoint response. Changed payout_allowed from string to boolean
• Execute a transfer request: Removed non existing field end_to_end_id from the response
• GET Tax Exemption : Removed reference field from the Response

• Index accounts for a person: Update missing datapoint

• Account Opening: Added new validations rules to account opening.

• Safeguarding Accounts: Added a new guide for the new safeguarding accounts product. Check this guide for more information on the key features of the product and how to integrate it into your solution.

• SDD notifications: Added a new feature for SDD notifications, which allows you to fetch pending SDDs and trigger notifications for your customers before the SDD execution date. The feature includes a new endpoint and a webhook event:

  • GET Fetch pending SDDs for an account
  • SEPA_DIRECT_DEBIT_TRANSACTION_SCHEDULED

Changed

• GET Index account bookings: Added a new booking type SepaInstantCreditTransferReturn.
• POST Create an account opening request: Added new values for the field product_name. The new values are for the subaccounts product and include the following:
  • SUBACCOUNT_CONSUMER_FRANCE
  • SUBACCOUNT_CONSUMER_GERMANY
  • SUBACCOUNT_CONSUMER_ITALY
  • SUBACCOUNT_CONSUMER_SPAIN
  • SUBACCOUNT_BUSINESS_FRANCE
  • SUBACCOUNT_BUSINESS_GERMANY
  • SUBACCOUNT_BUSINESS_ITALY
  • SUBACCOUNT_BUSINESS_SPAIN
  • SUBACCOUNT_FREELANCER_FRANCE
  • SUBACCOUNT_FREELANCER_GERMANY
  • SUBACCOUNT_FREELANCER_ITALY
  • SUBACCOUNT_FREELANCER_SPAIN The following values have been removed:
  • SUBACCOUNT_FRANCE
  • SUBACCOUNT_GERMANY
  • SUBACCOUNT_ITALY
  • SUBACCOUNT_SPAIN

• Savings Accounts
  • Added a new endpoint POST Request the utilization details of a person's tax exemption order to request tax exemption utilization details for an account.
  • Added a new webhook event TAX_EXEMPTION_UTILIZATION

Changed

• POST Create a business: Added a missing field to the request body nace_code.
• Legal and Compliance Screens guide: Updated the legal text of FATCA indication screens for B2B customers for Digital Banking & Cards product, including new screens on how to collect the FATCA indication for the business's legal representatives and beneficial owners.
• Savings Accounts: Updated the enum values for the field status in the response body of the following resources to include a new status FAILED:
  • POST Map a person's main account to a savings account
  • POST Map a business' main account to a savings account
  • DEPOSIT_ACCOUNT_UPDATED Webhook event

• Business resource creation on Sandbox: When creating businesses on Sandbox, please ensure that each business you create has unique values for the following fields name, postal_code, legal_form, and registration_number (if provided) to avoid receiving a 400 error.

Changed

• CARD_AUTHORIZATION webhook event:
  • Updated the webhook payload to add missing fields. New fields added include partner_id, fx_markup, issuer_fee in the meta_object.
  • Changed the meta_info field to be JSON-serialized object.
  • Updated the enum values possible for the field pos_entry_mode to include the following values: ECOMMERCE, CREDENTIAL_ON_FILE, MANUAL_PAN_ENTRY, CONTACTLESS, UNKNOWN, CHIP, MAG_STRIPE.
• POST Create a person: Added a note that disabling certain partner settings will restrict the number of NACE codes available.

• Bankident guide: Updated the flow diagram to include an additional SCHUFA check done in the beginning with the customer's data to determine their eligibility.
• GET Retrieve business registration number and issuer: Updated the response to an array of objects instead of a single object.
• GET Search for business's commercial registration: Updated the type of the field legal_representatives to an array of objects instead of a single object.
• Data collection: Removed the field data_terms_signed_at from the mandatory data points for businesses in all branches and products.

• POST Request fee summary statement: Added a new endpoint to request the creation of a fee summary statement. The guides Account management and Postbox have been updated accordingly.
• Cards API: New API endpoint: GET Retrieve card delivery tracking

Changed

• CARD_FRAUD_CASE_TIMEOUT webhook event: Updated the webhook payload to fix the example values for the field amount and original_amount.
• CARD_FRAUD_CASE_PENDING webhook event: Updated the webhook payload to fix the example values for the field amount and original_amount.
• POST Create an identification endpoint: Updated the possible values of the field idnow_process_type to include null.
• [GET Retrieve a person's tax exemption status endpoint][def]: Added new enum values to the status response property: INACTIVE, DELETED, EXPIRED, INVALID. Removed the CLOSED enum value.

Deleted

• Removed API endpoints related to the legacy Securities Brokerage product.

• SEPA Instant Credit Transfers guide: Added a new section with instructions for testing on Sandbox.

• Savings Account API: New endpoints added:
  • GET Retrieve interest details for a person's savings account
  • GET Retrieve interest details for a business' savings account

• Added new headers to the 200 response of the endpoints listed below: Total, Per-Page, Link
  • GET /v1/persons/{person_id}/accounts/{account_id}/topups
  • GET /v1/accounts/{account_id}/transactions/fees
• POST Create a fee collection transaction: New request property: valuta_date
• Device management API: Added more details and enum values to all 4xx responses.

• Cards API: New endpoint added: GET Index card transactions
• Postbox API: Added new endpoints for testing Postbox:
  • POST Upload document and create Postbox item for a Person
  • POST Upload document and create Postbox item for a Business
• API reference - Standards guide: Added a new section to the SEPA characters guide around replacing non-standard Latin characters in customer names according to European Payment Council guidelines.

Changed

• Instant SCT guide: Updated the requirements to indicate that supporting incoming Instant SCTs will be mandatory starting from 09.01.2025.
• Postbox API: Marked the following Postbox testing APIs as deprecated:
  • POST Create a Postbox item for a person
  • POST Create a Postbox item for a business

• Freelancer Overdrafts Guide: Added a note about the validations done upon overdraft termination request.

• BKYC guide and Onboard a Business guide: Updated the compliance questions section and added details on how to handle required compliance documents.

• Cards creation and servicing guide: Removed the deprecated "Report a card as lost/stolen" endpoint from the card status flow diagrams and their accompanying descriptions.

• Account closure guide: Added a hint that you may only close a customer's account with the reason account_revocation within 14 days of the account opening.

Changed

• ACCOUNT_OPENING_REQUEST webhook event: Changed the error response property to an object that contains the properties code and detail.
• SEPA_TIMED_ORDER webhook event: Updated the time format of the processed_at property.
• GET Index reservations on an account. Version 2022-07-18: The meta_info property is no longer enclosed in a cards object and is now returned at the same level as all the other response properties.
• Instant Top-Ups guide: Corrected the Top-Up status values in the flow diagram resulting from the success/failure of the Top-Up.

• AML update process guide: Changed the review cycle for high-risk customers in Germany from "once every two years" to "yearly."
• Mandatory features guide, Credit cards guides: Added a note that partners should not implement the Account Closure feature in their solutions if they use credit cards and do not use Digital Banking accounts.

Deleted

• Card creation & servicing guide: Removed the statement that you can only create up to five virtual cards per customer.

• Account Closure guide: Fixed an error in the guide in a webhook event name from ACCOUNT_CLOSURE_STATUS_UPDATE to the correct name ACCOUNT_CLOSURE_REQUEST_UPDATE. Updated the flow diagrams accordingly with the correct names.

• Business Onboarding requirements: The fields terms_and_conditions_signed_at and data_terms_signed_at are removed from the mandatory data points required for legal representatives and authorized persons. These fields are only needed for the business as a legal entity.
• DELEGATE_SCA_CANCEL: Added a note that this webhook event is not relevant for the new 3DS flow using change request. It's used only for the old flow, which will be deprecated soon.
• POSTBOX item response: Updated the description of the fields customer_notification and customer_confirmation.

• Account Closure guide: Restructured the guide and add flow diagrams for different ACR types. Please note that automated account closures are now a mandatory feature.
• ACCOUNT_CLOSURE_REQUEST webhook: Updated the example value of the field updated_at to the correct format.
• BOOKING webhook: Updated the example value of the field recorded_at to the correct format.

• Consumer Splitpay: Added additional information about the different events that trigger credit line webhook events.
• Freelancer Overdrafts: Added a new endpoint to request the termination of a freelancer overdraft.

Changed

• Customer Due Diligence: Corrected the color of the following CDD statuses to be yellow: NOT_SCORED, NOT_SCREENED, and NOT_VETTED. Adjusted also the appendix accordingly.
• Consumer Overdrafts API: Updated the response payload of the following endpoints to include new values for the field overdraft status. New values: defaulted_pending, conditions_termination_pending and termination_pending:
  • GET Retrieve a consumer overdraft
  • GET List all consumer overdrafts
  • Consumer overdraft guide
• Securities purchases API: Marked these endpoints as deprecated, as they correspond with a legacy product that Solaris no longer offers.

• Card creation & servicing guide: Synchronized the instructions for replacing a card/reporting a card as lost or stolen with the description in the API reference.
• Card tokenization APIs: Renamed the "Visa tokens servicing" API reference subsection to "Card token servicing."
• PSD2 guide: To comply with PSD2 regulations, you need to implement app-to-app redirection if a user is using a TPP mobile app, and also has a banking app installed. The user must be redirected to the banking app to perform the 1FA login. The guide has been updated with implementation recommendations, as well as the user flow.

• POST Create an account opening request: Added new product_name values for the Savings Account product and values with specific product/customer/branch naming:
  • DECOUPLED_CARD_CONSUMER_GERMANY
  • EMONEY_ACCOUNT_BUSINESS_GERMANY
  • EMONEY_ACCOUNT_CONSUMER_GERMANY
  • EMONEY_ACCOUNT_FREELANCER_GERMANY
  • RESTRICTED_ACCOUNT_BUSINESS_GERMANY
  • SAVINGS_ACCOUNT_CONSUMER_FRANCE
  • SAVINGS_ACCOUNT_BUSINESS_FRANCE
  • SAVINGS_ACCOUNT_FREELANCER_FRANCE
  • SAVINGS_ACCOUNT_CONSUMER_GERMANY
  • SAVINGS_ACCOUNT_BUSINESS_GERMANY
  • SAVINGS_ACCOUNT_FREELANCER_GERMANY
  • SAVINGS_ACCOUNT_CONSUMER_ITALY
  • SAVINGS_ACCOUNT_BUSINESS_ITALY
  • SAVINGS_ACCOUNT_FREELANCER_ITALY
  • SAVINGS_ACCOUNT_CONSUMER_SPAIN
  • SAVINGS_ACCOUNT_BUSINESS_SPAIN
  • SAVINGS_ACCOUNT_FREELANCER_SPAIN

Deleted

• POST Create an account opening request: Removed product_name values that do not include product + customer + country:
  • DECOUPLED_CARD_CONSUMER
  • DECOUPLED_CARD_BUSINESS
  • EMONEY_ACCOUNT_CONSUMER
  • EMONEY_ACCOUNT_FREELANCER
  • EMONEY_ACCOUNT_BUSINESS
  • RESTRICTED_ACCOUNT_BUSINESS

• New product: Savings Accounts (Tagesgeld)
  • Product guide
  • API endpoints

Changed

• Card spending controls API: Corrected the name of a property in the V2 card spending control limit endpoints from exclusion_dimension to excluded_dimension.

Deleted

• All documentation around Solaris Digital Assets has been removed.

• New webhook event: CREDIT_CARD_BILL
• Card spending controls: Solaris has released V2 of the card spending limit controls endpoints. The card spending controls guide has been updated with instructions on how to use these new endpoints.
  • POST Create card spending limit control (V2)
  • GET Retrieve a card spending limit control (V2)
  • GET Index card spending limit controls (V2)
  • DELETE Remove a card spending limit control (V2)

Changed

• POST Create a secure view for card details: Added more instructions for generating the signature. The API reference now contains more details on how to generate a single string from the jwk_key representation of the public part of the rsa_key.