For Agents
Manage submerchants, run self-onboarding with KYC and bank accounts, and define, schedule, and download financial reports across 27 endpoints. Authenticates with a bearer token obtained via OAuth2 client credentials.
Use for: Create a new submerchant on the payment platform, List the submerchants under our account, Start a draft submerchant onboarding and submit it for review, Invite a submerchant to onboard themselves
Not supported: Does not process card charges, capture payments, or issue refunds. Use for submerchant management, self-onboarding, KYC, and financial reporting only.
The Dalenys (now Payplug) Payment Platform API supports marketplace and payment facilitator integrations. Across 27 endpoints it issues OAuth2 access tokens, manages submerchants and their self-onboarding including KYC and bank accounts, and defines, schedules, and downloads financial reports.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dalenys Payment Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdalenys.com%2Fdalenys" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdalenys.com%2Fdalenys" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Dalenys Payment Platform API.
Obtain a bearer access token via the OAuth2 client credentials flow
Create, list, update, and delete submerchants
Run self-onboarding for draft submerchants, bank accounts, and KYC
Invite submerchants to onboard themselves
Define report planners and schedule report executions
Download generated financial reports as CSV
Patterns agents use Dalenys Payment Platform API for, with concrete tasks.
★ Agent-Driven Submerchant Onboarding
An AI agent connected through Jentic can move a new seller through onboarding without a human working the dashboard. It creates a draft submerchant, attaches bank account details, and submits the draft for KYC review, or sends an invitation for the submerchant to complete onboarding themselves, keeping a marketplace's seller pipeline moving.
Create a draft submerchant, add its bank account, and submit the draft for KYC review
Automated Financial Reporting
Finance teams need settlement and transaction reports on a schedule. The Dalenys API defines report planners, triggers immediate executions, and downloads the resulting CSV, so an agent can schedule a recurring report and fetch each run's file for reconciliation.
Create a report planner for weekly settlement, trigger an execution, and download the CSV once it is ready
Submerchant Lifecycle Management
Marketplaces need to keep submerchant records current. The Dalenys API lists submerchants, reads a submerchant's details, and updates or removes one, letting an agent reconcile the payment platform against a marketplace's own seller list and correct drift automatically.
List submerchants, find one whose details no longer match the marketplace record, and update it
27 endpoints — the dalenys (now payplug) payment platform api supports marketplace and payment facilitator integrations.
METHOD
PATH
DESCRIPTION
/iam/token
Request an OAuth2 client credentials access token
/payment_facilitator
Create a submerchant
/payment_facilitator
List submerchants
/selfOnboarding/draftSubmerchants/{draftSubmerchantId}/submit
Submit a draft submerchant for KYC review
/reports/executions/{executionId}/download
Download a report CSV
/iam/token
Request an OAuth2 client credentials access token
/payment_facilitator
Create a submerchant
/payment_facilitator
List submerchants
/selfOnboarding/draftSubmerchants/{draftSubmerchantId}/submit
Submit a draft submerchant for KYC review
/reports/executions/{executionId}/download
Download a report CSV
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Dalenys by hand means running the OAuth2 client credentials flow against the token endpoint, refreshing the bearer token, and sequencing the onboarding and reporting calls yourself. Through Jentic you install once, import Dalenys from the API Directory, store your client credentials once, and your agent calls the operations directly.
Permission scoping
Submerchant, planner, and report operations address a record by its ID in the URL path, so a rule can bound your agent to specific submerchants or reports as well as to specific operations. You might allow reading submerchants and downloading reports while blocking submerchant deletion.
Credential isolation
Your Dalenys client credentials are stored once, encrypted, by your own Jentic One instance, which obtains and injects the bearer token at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'download a Dalenys report as CSV', and Jentic returns the matching operation with its input schema so the agent calls it with the right execution ID.
Alternatives and complements available in the Jentic catalogue.
Specific to using Dalenys Payment Platform API through Jentic.
What authentication does the Dalenys Payment Platform API use?
Requests use a bearer token in the Authorization header, obtained by posting to the token endpoint with the OAuth2 client credentials flow, per its OpenAPI spec. The token endpoint itself is open. Through Jentic your client credentials are stored once by your own self-hosted instance and the token is obtained and injected when the agent calls, so they never appear in the agent's prompt or logs.
Is there a Dalenys MCP server?
You don't need an MCP server to give your agent the Dalenys Payment Platform API. Jentic connects it directly from the API Directory: import it, store your client credentials once, and your agent calls the submerchant, onboarding, and reporting operations. Operations are discovered on demand, so nothing extra loads into the agent's context.
Can I limit what my agent is allowed to do with the Dalenys Payment Platform API?
Yes. Submerchant, planner, and report operations address a record by its ID in the URL path, so a rule can bound the agent to specific submerchants or reports as well as to specific operations. You might allow reading submerchants and downloading reports while blocking submerchant deletion, with every call logged.
Can the Dalenys API onboard submerchants automatically?
Yes. The self-onboarding operations create draft submerchants, attach bank accounts, and submit drafts for KYC review, and there is an invitation operation so a submerchant can complete onboarding themselves, letting an agent drive either path.
What are the rate limits for the Dalenys Payment Platform API?
The OpenAPI spec does not specify rate limits. Check the Dalenys developer documentation at https://developer.dalenys.com for current limits before running high-volume onboarding or reporting jobs.
How do I download a report through Jentic?
Search Jentic by intent, for example 'download a Dalenys report as CSV', and Jentic returns the download operation with its input schema. Your agent supplies the execution ID and reads back the CSV. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED