Sterling B2B Integrator Acting as Third Party

The Sterling B2B Integrator can act as a Third Party either in T-Copy mode or Y-Copy mode. As a Third Party, SWIFT forwards the copied request messages to the Sterling B2B Integrator. When the copied request is received, based on the Service Name specified in the message, the Sterling B2B Integrator searches the SWIFTNet Copy Service Profile to find out whether the Sterling B2B Integrator must act in T-Copy or Y-Copy mode.

In SWIFTNet 7, SWIFT supports 2 Copy Type: Header or Full. So, it depends on the Copy Type. If Copy Type = Header, the Enhanced Header Information is extracted and put into the mailbox. However, if Copy Type = Full, the whole request XML is put in the mailbox (because if Copy Type = Full, the Enhanced Header Info does not need to exist).

You can create a mailbox routing rule to evaluate this mailbox and bootstrap a custom business process to make the decision whether to authorize as a third party (Third Party Authorised option) or refuse (Refuse option) the copied request based on the Enhanced Header Information or the full payload that has been received (depends on the Copy Type Header or Full).

In SWIFTNet 7.0, the application does not provide a sample approval/refusal process but you may use SWIFTNet Client Profile feature to approve/refuse manually.