Apiture Developers Apiture Developers

Menu

  • Explore API Banking
    • API Digital Banking
    • Embedded Banking
    • Contact Us
  • Developers
    • Quick Start Guide
    • Embedded Banking
    • Events Reference
    • Authenticated Portal
  • API Documentation
    • Reference
Log In / Register
Apiture Developers Apiture Developers
Log In / Register
Apiture Developers

Menu

  • Explore API Banking
    • API Digital Banking
    • Embedded Banking
    • Contact Us
  • Developers
    • Quick Start Guide
    • Embedded Banking
    • Events Reference
    • Authenticated Portal
  • API Documentation
    • Reference

Embedded Banking

  • folder icon closed folder iconGetting Started
  • folder icon closed folder iconConcepts
    • Overview
    • Managing User Credentials
    • Components
    • Registering your Application
    • Terminology
    • Encryption and Authentication
  • folder icon closed folder iconGuides
    • Component Customization
    • Customization Examples
    • Initializing Components
    • Event Handling and Data Processing
  • folder icon closed folder iconRelease Notes
    • EB v1.0 Release Notes
    • EB v1.2.2 Release Notes
    • EB v1.3 Release Notes
    • Developer Portal 1.0 Update

EB v1.3 Release Notes

  • folder icon closed folder iconAPI Documentation
    • Getting Started
    • Concepts
      • API Keys
      • Authorization and Authentication
      • Access Tokens
      • Resources and URI Structure
      • Resource Collections
      • Resource Sets
      • Scopes & Entitlements
      • Error Responses
      • Error Types
      • Dry Runs
      • Markdown
      • Idempotent Operations
      • Collection Pagination
      • Collection Filtering
      • Transfers
      • Business Transfers
      • Cutoff Times
      • Identity Challenges
    • Guides
      • Authenticate Users in your App using OpenID Connect with PKCE
      • Authenticate using OAuth 2.0 Client Credentials Flow
      • Getting a List of Accounts
      • Listing the Balances for Accounts
      • Using Pagination
      • Creating a One-Time Transfer
      • Listing Transfers
      • Retrieving Business Transfer Information
      • Completing an Identity Challenge
    • API Reference
    • Release Notes
  • folder icon closed folder iconAuthenticated Portal
    • Getting Started
      • Registration
      • Profile
    • Concepts
      • Environments
      • Products
    • Managing your Applications
      • Creating Applications
      • Creating Data Direct: Real-Time Webhooks
      • Editing Applications
      • Application Owners
      • Getting Application Keys and IDs
      • Continue your Project
    • Release Notes
      • Developer Portal 1.0
      • Developer Portal 1.1
  • folder icon closed folder iconEmbedded Banking
    • Getting Started
    • Concepts
      • Overview
      • Managing User Credentials
      • Components
      • Registering your Application
      • Terminology
      • Encryption and Authentication
    • Guides
      • Component Customization
      • Customization Examples
      • Initializing Components
      • Event Handling and Data Processing
    • Release Notes
      • EB v1.0 Release Notes
      • EB v1.2.2 Release Notes
      • EB v1.3 Release Notes
      • Developer Portal 1.0 Update
  • folder icon closed folder iconEvents
    • Introduction
    • Guides
      • General Structure
      • Field Annotations
      • Customer Onboarding Data Direct: Real-Time
    • Data Delivery
      • Flat File Delivery
      • Snowflake Delivery
      • Event History API
      • Real-time / Webhooks

EB v1.3 Release Notes

INTRODUCTION

Call to Action Component

Apiture is releasing it’s fourth embedded banking component – Call To Action V1.0

The Call To Action (CTA) Component will enable a Financial Institution (FI) to configure static, customizable messaging that will display inside the partner applications with a call to action (CTA) of their choice that can link users out to any digital location. This link is a configurable URL and supports linking to pages on the FI’s website or any other website of the FI’s choice. Embedded Banking is agnostic as to where the FI wants to drive its prospective and/or active user base, and can support sending users to any flow that is desirable to achieve the Financial Institution’s goals within the partner channel.

Component Configuration

Apiture is taking steps to make Embedded Banking (EB) more accessible to EB partners who include embedded banking components in their applications. While Apiture staff is able to provide guidance when configuring an EB component in an application, every partner should also be able to make any configuration changes available to them whenever they desire.

This update provides:

  • Separated Financial Institution (FI) and EB Partner configurations on the backend

  • Exposes FI & EB Partner Configurations so they can be set and changed by appropriate audiences

  • Empower EB Partner developers to set and change EB Partner configurations in code without having to involve Apiture

  • Empower Apiture employees to set and change EB Partner configurations, if desired by the Partner or FI

FEATURES

Configuration Customization

Embedded Banking Partners can now adjust any configuration changes without needing to contact Apiture. The configuration for components are now managed within a JSON file that is stored by the Partner in an accessible location for their application, and can be updated whenever it is needed. Apiture no longer needs to be contacted to make configuration changes.

For example, the title of the component “Accounts & Balances” can be customized along with the color, font & size.

The accounts and balances component is edited in the gallery app.

For information on the parameters that can be adjusted, see Component Customization – Apiture Developers .

CTA Component

  • The Call To Action (CTA) Component will look the same regardless of the user’s connection status, meaning it will always look the same whether the end user is Unauthenticated or Authenticated.

  • The FI configures the messaging for the Call To Action (CTA) Component

  • The FI can design multiple Call To Action (CTA) Components per partner.

  • The CTA Component can be embedded on any page, even if it is the only component used.

CTA component configuration

The Financial Institution is able to determine the content for the Call to Action Component as a reflection of their desired branding and messaging for EB Partners. Configurable items include a primary link, a optional image, an optional header, and other customizable text.

How can we help?

Get support for your issues.

Explore API Banking

  • API Digital Banking
  • Embedded Banking
  • Contact Us

Developers

  • Get Started Guide
  • API Reference
  • Embedded Banking

More

  • Apiture.com

Privacy Policy

© 2023 Apiture Inc.   |   All Rights Reserved