Skip to main content
When migrating from Elements to Opal, there are several key changes to consider:

​
URL Changes

If you’re launching Opal directly from a URL, the process remains similar to Elements, but with updated domains:
  • Elements: elements.{environment}.methodfi.com
  • Opal: opal.{environment}.methodfi.com

​
New Libraries

We’ve introduced new SDKs specifically designed for Opal integration: See our libraries documentation for detailed implementation guides.

​
Token Generation Changes

When generating tokens for Opal, we’ve added new parameters that must be provided in order for more flexibility and control over the user experience. The token generation process has been streamlined in Opal.

​
Elements

POST /elements/token
{
  "type": "connect",
  "connect": {
    "entity_id": "ent_au22b1fbFJbp8",
    "products": ["balance"],
    "redirect_url": "https://example.com/callback"
  }
}

​
Opal

POST /opal/token
{
  "mode": "connect",
  "entity_id": "ent_au22b1fbFJbp8",
  "connect": {
    "selection_type": "single",
    "account_filters": {
      "include": {
        "account_types": ["credit_card", "auto_loan"],
        "products": ["balance"]
      }
    }
  }
}
In Elements, product filtering was a top-level field (connect.products). In Opal, product filtering is done via connect.account_filters.include.products. Allowed values: balance, sensitive, payoff, update, payment. See Opal Identity, Connect, Card Connect, and Account Verification guides for more info on token generation.