Skip to main content

Migrated users guide

If you are a user of Fena Partner Portal and wish to switch to the new version, please contact us at support@fena.co. We will transfer all your account settings, data, and merchant information to the new portal. Once your data is migrated, we will notify you, and you can log into your account on the new portal using the credentials from your old Partner Portal account. Please also review the documentation for the Partner Portal Toolkit at Toolkit Docs.

API Keys​

In the Toolkit, API key settings have been expanded. You can now set redirect URLs and webhook URLs, which will be used to send information during merchant verification flow and bank account connection flow. By default, all migrated keys from the old portal retain the same webhook and redirect URLs if they were specified on the old portal settings page at API Keys Settings. If these details were not provided in the old settings, please update the API key settings with the necessary webhook and redirect URLs to receive notifications about merchant or bank account status changes.

Additionally, the Toolkit now features a role-based system. Each migrated API key receives the default role "Partner Integration," allowing all Partner API operations. If you wish to change the API key permissions, you can create a customized role and assign it to the API key or create a new API key with this role.

API Changes​

General API Changes​

Changes to Request Paths​

To work with the Toolkit Partner API, change the server address from https://business.api.fena.co/public-partner/ to https://epos.api.fena.co/open/partner/.

Changes to Request Headers​

  • For API key authorization, instead of a single key-value pair (apisecret), you need to provide two key-value pairs: terminal-id (ID of the API key) and terminal secret (formerly apisecret).

Changes in Fetching Data​

  • All endpoints returning a list of data now support pagination. To navigate paginated lists, add the query parameter page, e.g., list?page=1.

Merchant Management​

Changes to Request Paths​

  • Added /info to the request subpath: /companies/create => /companies/info/create.

Changes to Request and Response Data​

  • CustomWebhookURL: We will send webhook notifications about merchant verification status updates or bank account status updates to this URL instead of the API key webhook URL or the URL specified in account settings.
  • CustomRedirectURL: Your managed company will be redirected to this URL after passing the verification flow instead of the API key redirect URL or the URL specified in account settings.
  • sendInviteToUser: A boolean field in the request payload. We will send an email with registration instructions to the managed company contact.

Link to the old API specification
Link to the new API specification

Merchant Bank Accounts API​

Changes to Request Paths​

  • Changed request subpath companies/{companyId}/bank-account/ => companies/{companyId}/bank-accounts/
  • Changed request suffix for create bank account endpoint path companies/{companyId}/bank-account/new => companies/{companyId}/bank-accounts/create

Changes to Request and Response Data​

  • Added mandatory field bankStatementAttachmentURL: This field should contain a link to the bank statement file.

Link to the old API specification
Link to the new API specification

Merchant Integrations API​

Changes to Request and Response Data​

  • Removed field bankAccount: A bank account is no longer required to create an integration.

Link to the old API specification
Link to the new API specification

Merchant Payments​

Single Payments API​

Changes to Request Paths​

  • Request subpath changed: /companies/{companyID}/payments/ => /companies/{companyID}/payments/single/.

Changes to Request and Response Data​

  • Renamed the field invoiceRefNumber to reference.
  • Fields bankAccount and integration are no longer mutually exclusive and can be sent together.

Link to the old API specification
Link to the new API specification

Recurring Payments API​

Changes to Request Paths​

  • Request subpath changed: /companies/{companyID}/recurring-payments/ => /companies/{companyID}/payments/recurring/.

Link to the old API specification
Link to the new API specification

Transactions API​

Link to the old API specification
Link to the new API specification

  • Request subpath changed: /companies/{companyID}/transactions/ => /companies/{companyID}/payments/transactions.
  • Changed request suffix for transactrions statistics endpoint companies/{companyId}/bank-account/new => companies/{companyId}/bank-accounts/create /companies/{companyID}/transactions/stats => /companies/{companyID}/payments/transactions/statistics

Changes to Request and Response Data​