Business Transaction Format configuration

EBICS 3.0 replaces the use of banking order types (or file formats) with Business Transaction Format (BTF) service attributes.

BTF Service contains the following attributes:
  • BTF structure
  • ServiceName (*): [A-Z0-9] length=3
  • Scope: [A-Z0-9] length=2 to 3
  • ServiceOption: [A-Z0-9] length=3 to 10
  • Containerflag: [A-Z0-9] length=3
  • MsgName (*): [a-z.0-9] length=1 to 10, for example pain.001. The MsgName attribute can have 3 optional attributes:
    • variant: [0-9] length=3
    • version: [0-9] length=2
    • format: [A-Z0-9] length=1 to 4

BTF Service operations

You can perform the following BTF Service operations both using the UI and REST APIs.
  • create BTF service
  • read BTF service
  • update BTF service
  • delete BTF service

Using the UI

You can log in to the Sterling B2B Integrator Server or Client either as an EBICS Administrator or EBICS Operator.

On EBICS Client, click BTF Services from the Profile Management menu to access BTF Services and perform all the operations.

On EBICS Server, click BTF Service Configuration from the Administration menu > EBICS > Order Type Manager to access BTF Services and perform all operations.

Using REST APIs

You can use the BTF Services REST API to perform the CRUD operations. For more information, see B2B REST APIs available in Sterling B2B Integrator.

BTF Service permissions

The following is the UI permission to be assigned for users to perform BTF Service CRUD operations:

UI EBICS BTF Service Configuration (EBICS_BTF_SERVICE_CONF)

You can navigate to Administration Menu > Accounts > User Accounts and configure the following permissions:

  • API/GET/btfserviceget
  • API/POST/btfservicecreate
  • API/PUT/btfserviceupdate
  • API/DELETE/btfservicedelete