Scenarios

Test message generation for StoneX

DD-100: :50K: and :59: carry only name + one address line (no town, no country). Without a town the address is not hybrid, so even with HYBRID_ADDRESS=true the pacs.008 keeps today's AdrLine-only PstlAdr (no TwnNm/Ctry). The hybridAddress assertion only checks that the run happened with the switch on.

DD-100: :50K: and :59: carry name / address / town but no country line (line 4 missing). The country falls back to the BIC: Dbtr Ctry US = characters 5-6 of the MT receiver BIC CITIUS33XXXX (block 2), Cdtr Ctry JM = characters 5-6 of the MT sender BIC FILBJMKNAXXX (block 1). Requires HYBRID_ADDRESS=true on the ynohub-templates service (and no routing option addressFormat=unstructured); with the switch off the output is today's AdrLine-only block and these assertions fail by design.

DD-100: outgoing MT103 whose :50K: and :59: carry name / address / town / country (10 BIRDSUCKER HEIGHTS / TOWNHOUSE 35 / JM and HOOGSTRAAT 6 / BRUSSELS / BE). The pacs.008 Dbtr and Cdtr PstlAdr must be hybrid: TwnNm, Ctry, AdrLine (schema order). Requires HYBRID_ADDRESS=true on the ynohub-templates service (and no routing option addressFormat=unstructured); with the switch off the output is today's AdrLine-only block and these assertions fail by design.

DD-100: same MT103 as the 4-lines case but line 4 is a country NAME (JAMAICA / BELGIUM). The name is looked up to ISO 3166 alpha-2, so the pacs.008 PstlAdr Ctry must be JM / BE. Requires HYBRID_ADDRESS=true on the ynohub-templates service (and no routing option addressFormat=unstructured); with the switch off the output is today's AdrLine-only block and these assertions fail by design.

Test FGB Return Flow for MT202 .

Check if the transaction is a fedwire message

Test if MX message header contains "stp" request Sup Type . Message is route to STP in Swift

DD-116: an MT195 /REJT/AC01 whose :21: is the MT103 :20: (= last 16 chars of the pacs.008 InstrId S0652393CAA101) and no copied :32A:. Run a 'swift.pacs.008 DD-116 Return' or 'swift.pacs.008 DD-102 Response Tracking' first. The newest incoming payment with that InstrId goes to RETURN / AC01; the pacs.004 falls back to the original amount and today's value date.

DD-102: an MT199 with :79://ACSP/G003 (awaiting value date) on the newest incoming pacs.008 with InstrId S0652393CAA101 (the 'swift.pacs.008 DD-102 Response Tracking' message) sets the payment to ACSP with reason G003 and renders a trck.001 with transactionStatus ACSP / reasonCode G003 for the Tracker. Run a pacs.008 DD-102 first; the ACSP is refused only when that payment is already ACCC/RJCT.

MX Settlement date must take the MT103 32A field date . It used to pick the date today date automatically

MX Settllement date must take the MT103 32A field date . It used to pick the date today date automatically

Test if the routing code for MT field 57D is translated correctly

DD-100: incoming pacs.008 whose Dbtr/Cdtr PstlAdr is hybrid (TwnNm, Ctry, one AdrLine). The MT103 :50K: / :59: must print name, then AdrLine, TwnNm, Ctry on lines 2-4. Requires HYBRID_ADDRESS=true on the ynohub-templates service (and no routing option addressFormat=unstructured); with the switch off the output is today's AdrLine-only block and these assertions fail by design.

DD-100: incoming pacs.008 with TwnNm, Ctry and two AdrLine of about 60 chars. The AdrLines are joined with one space and cut to 35 chars (mtMaxLenNameAndAddress) on :50K: / :59: line 2; TwnNm on line 3, Ctry on line 4. Requires HYBRID_ADDRESS=true on the ynohub-templates service (and no routing option addressFormat=unstructured); with the switch off the output is today's AdrLine-only block and these assertions fail by design.

DD-100: incoming pacs.008 with a structured-only PstlAdr (StrtNm, BldgNb, PstCd, TwnNm, Ctry, no AdrLine). :50K: / :59: line 2 = 'StrtNm BldgNb, PstCd' cut to 35, line 3 TwnNm, line 4 Ctry. Requires HYBRID_ADDRESS=true on the ynohub-templates service (and no routing option addressFormat=unstructured); with the switch off the output is today's AdrLine-only block and these assertions fail by design.

MX Settllement date must be put in the 32A field date . It used to pick the date today date automatically

DD-116: sends the incoming pacs.008 (InstrId S0652393CAA101) and, as auto follow-up, an MT195 /REJT/AC04 whose :21: is that pacs.008 MsgId. The follow-up must resolve the incoming payment (status RETURN / AC04), render the pacs.004 with template swift-pacs004 and hand it to FINASTRA_SERVICE.

DD-101: pain.001 ChrgBr SLEV maps to F71A SHA.

DD-101: creditor name longer than 35 chars is split into max 4 x 35-char lines, no truncation. PIN paths + expected lines before enabling.

DD-101: incoming pain.001.001.09 renders an MT101. F20=GrpHdr/MsgId, F30 execution date as YYMMDD, 32B amount with comma. PIN assertion paths to final mt101 var names before enabling.