Jump to Content
Minna TechnologiesDocsConsoleSupport
GuidesRecipesAPI Reference
DocsConsoleSupportMinna Technologies
GuidesRecipesAPI Reference

Introduction

  • Overview
  • Quick start
  • User journey
    • Example: Transaction entry point
    • Example: Subscription Overview
    • Example: Search entry point

Core Concepts

  • Authentication
    • Client namespace
  • Users
    • Manage users
    • Locales
    • API reference
  • Subscription merchants
    • API reference
  • Insights
    • Insight lifecycle
    • Cancel Insights
    • Identify Insights
    • API reference
  • Integration options
    • Native
    • WebUI
  • API versioning
  • Error handing
  • Sandbox
  • Console
    • Key management
    • Cancellation management

Before action: entry points

  • Entry point introduction
  • Transaction Overview: Merchant Sync
    • Implementation guide
  • Transaction Overview: Transaction Rules
    • Implementation guide
  • Subscription Overview
    • Identify
    • Identify user flows
    • Implementation guide: Identify WebUI
  • Search entry point
    • Implementation guide - WebUI

During action: Action feature flows

  • Cancel
    • Cancel Native
    • Cancel WebUI
    • User flows
    • End to end testing
    • API reference

After action: User messaging

  • User messaging solutions
    • Direct user messaging
    • Re-entry
  • Sourcing user messages
    • Push: Webhooks
    • Push: Webhooks - API reference
    • Pull: API

Security

  • Security overview
  • API security
  • Compliance
  • Data management

Contact

  • Technical support
  • Sales

Example: Search entry point

Suggest Edits

Here we show how cancelling a subscription without the bank needing to identify it first.

Use cases:

  • The user have a subscription outside of the bank but want to cancel it
  • The identification at the bank does not cover the source the subscription is paid from (for example debit account).

Updated 2 months ago


Did this page help you?