Skip to main content
The new Mysoleas architecture clearly separates shared infrastructure from business domains. Infrastructure manages public entry points, identity, security, routing, and context. Business domains carry the products: payments, users, sales, notifications, and marketing campaigns.

​
Infrastructure and business domains

​
account.mysoleas.com

The account domain is Mysoleas Identity Cloud. It is a full service, not a simple technical dependency. Use it to:
  • integrate the Sign in with Mysoleas button;
  • authenticate a user with OAuth2/OIDC;
  • manage the identity and user layer of a third-party application;
  • obtain a JWT;
  • refresh or revoke a token;
  • read user claims with /oauth/v2/userinfo;
  • allow a third-party application to act in the context of an authorized user or customer.
This service can be used without the gateway. If your only need is to authenticate users and open a session in your own application, you can stop at Identity Cloud. To create an OAuth2 application, the user must have a Mysoleas account, sign in to the dashboard at https://mysoleas.com, then configure the application, redirect URLs, and scopes.

​
api.mysoleas.com

The API domain is the public gateway. Your integration should not call internal microservices directly. All gateway routes expect the JWT in the x-sp-auth-token header.
Use it to:
  • list countries;
  • list payment services;
  • verify active providers;
  • create and track collections;
  • create and track disbursements;
  • create payment links;
  • manage subscriptions;
  • drive the other business domains progressively exposed by Mysoleas.

​
Gateway authentication rule

The gateway always expects the same header:
This convention prevents confusion between gateway authentication and other headers used by providers, plugins, or frontends.

​
Business domains in the ecosystem

​
SoleasPay

SoleasPay is the Mysoleas payment service processor. It aggregates payment methods and exposes collection, disbursement, subscription, payment link, service, country, and provider flows.

​
Mysoleas Identity Cloud

Identity Cloud manages users, OAuth2 applications, JWT tokens, and claims. It can serve as a standalone identity service for a third-party application, or provide the JWT later used by the gateway.

​
MyShup

MyShup carries sales management and automation. It participates in commercial journeys, products, single-product or multi-product orders, and merchant operations.

​
Notification Service

Notification Service centralizes transactional communications: confirmations, alerts, system messages, and event-driven notifications. It also carries the V2 marketing API for contacts, audiences, templates, and campaigns, with Listmonk as the internal engine.

​
MyBoost

MyBoost covers marketing through boost campaigns, UGC challenges, promotions, customer activation, and marketing follow-up.

​
Standard payment flow

Collections and disbursements use a three-step model. This model prevents duplicate debits. It also gives you a clear recovery point after a network timeout.

​
SoleasPay plugin flow

SoleasPay v4 plugins do not follow the same model as server-to-server gateway calls. Use these plugins for a fast payment integration when you do not want to manage OAuth2, JWT, intent, execute, and status directly.

​
Context data

The gateway transports the user and tenant context through token claims. It can also forward some internal or trace headers.

​
Important states

A transaction can move through several non-final states before it completes. Treat COMPLETED, FAILED, CANCELLED, and REFUNDED as final states.