SWIFTNet Service Profile

The HeaderInfo block is optional, except for those services that mandate it. If the HeaderInfo block is not used, it must not be present, and if it is used, it must be validated by the schema.

The SWIFTNet Service Profile enables you to easily port Service Profiles from one application instance to another. This function allows you to associate SWIFTNet Request Type with a Schema for Header Validation. You need to create the SWIFTNet Service Profile and associate the request type with the selected schema. This allows the Sterling B2B Integrator to validate the HeaderInfo when it is present in the request.

Note: The schema must be saved in Sterling B2B Integrator.

The Request Type parameter can accept a wildcard (*) to be used only at the end of the string. To determine which Service Profile to be used for a particular Request Type, the Sterling B2B Integrator uses a best-match policy. For example, if there are two Service Profile defined, for pain.* and pain.001.*, and the actual request type is pain.002.001, then the first one will be selected.

Two SWIFTNet Service Profiles are preloaded into Sterling B2B Integrator. The pacs.* and pains.* service profiles are associated with the Transaction Count schema and set to Required for validation. The Transaction Count and Payment Summary schemas are also preloaded into the Sterling B2B Integrator.

You can also import and export SWIFTNet Service Profiles from one application instance to another.