Struct Field25NoOption 

pub struct Field25NoOption {
    pub authorisation: String,
}

Field 25: Account Identification / Authorisation

Purpose

Provides account identification or authorization information for payment instructions. This field serves dual purposes: identifying accounts for payment processing and providing security authorization codes between the ordering customer and the account servicing financial institution.

Format

• Swift Format: 35x (NoOption), /34x (Option A), 35x + 4!a2!a2!c[3!c] (Option P)
• Description: Account identifier or authorization code with optional BIC
• Character Set: Alphanumeric characters following Swift standards

Presence

• Status: Optional in most contexts, mandatory when account identification required
• Swift Error Codes: T61 (invalid account format), C05 (invalid BIC)
• Usage Context: Account services and authorization verification

Usage Rules

• Account Identification: Specifies account to be debited or credited
• Authorization Security: Contains security provisions between customer and institution
• Format Selection: Choose appropriate option based on account identification needs
• BIC Validation: When BIC provided, must be valid financial institution identifier

Network Validation Rules

• Account Format: Must conform to institutional account numbering standards
• BIC Validation: BIC must be registered financial institution code
• Character Validation: Only permitted characters in Swift character set
• Length Compliance: Must not exceed maximum field length restrictions

Field Options and Usage

NoOption (35x) - Authorisation

• Usage: Security authorization codes and digital signatures
• Length: Up to 35 characters
• Purpose: Authentication between customer and account servicing institution
• Security Context: Electronic device codes, digital signatures, or agreed tokens

Option A (/34x) - Account Identifier

• Usage: Simple account identification with slash prefix
• Length: Up to 34 characters (excluding slash)
• Purpose: Basic account identification for payment processing
• Format: Slash followed by account identifier

Option P (35x + BIC) - Account with Institution

• Usage: Account identification with associated financial institution
• Components: Account identifier + Institution BIC code
• Purpose: Complete account specification including servicing institution
• BIC Format: Standard 8 or 11 character BIC code

Business Context

• Payment Processing: Essential for routing payments to correct accounts
• Security Framework: Enables secure authorization between parties
• Account Services: Facilitates account-based financial services
• Cross-Border Payments: Provides institution identification for international transfers

Authorization Security

• Digital Signatures: Electronic signature verification codes
• Token Authentication: Security tokens generated by electronic devices
• Bilateral Agreements: Institution-specific authorization mechanisms
• Fraud Prevention: Additional security layer for payment authorization

Examples

:25:AUTH123456789         // Authorization code (NoOption)
:25A:/GB82WEST12345698765432  // IBAN account identifier
:25A:/1234567890          // Simple account number
:25P:CHF1234567890        // Account with BIC
    UBSWCHZH80XX          // Swiss bank BIC

Regional Considerations

• European Payments: IBAN format compliance for SEPA transactions
• US Payments: Federal routing number integration
• Asian Markets: Local account numbering standards
• Cross-Border: International account identification requirements

Account Format Standards

• IBAN: International Bank Account Number for European markets
• BBAN: Basic Bank Account Number for domestic transactions
• Local Formats: Region-specific account numbering schemes
• Institution Standards: Bank-specific account identification rules

Error Prevention

• Account Validation: Verify account exists and is accessible
• BIC Verification: Confirm BIC is valid and active
• Format Checking: Ensure account format matches regional standards
• Authorization Validation: Verify security codes are current and valid

Related Fields

• Field 50: Ordering Customer (account holder identification)
• Field 57: Account With Institution (receiving account details)
• Field 59: Beneficiary Customer (final account recipient)
• Field 52: Ordering Institution (account servicing institution)

Security Considerations

• Token Management: Secure generation and validation of authorization tokens
• Code Expiry: Time-limited validity of authorization codes
• Bilateral Security: Institution-specific security arrangements
• Audit Trail: Comprehensive logging of authorization attempts

STP Compliance

• Format Standardization: Consistent account format for automated processing
• Validation Enhancement: Enhanced security validation for STP transactions
• Exception Handling: Automated handling of authorization failures
• Quality Control: Real-time validation of account and authorization data

Compliance and Audit

• Regulatory Requirements: Meeting account identification regulations
• Security Documentation: Maintaining records of authorization methods
• Access Control: Ensuring proper account access authorization
• Investigation Support: Authorization tracking for compliance investigations

See Also

• Swift FIN User Handbook: Account Identification Standards

• Authorization Guidelines: Security Code Requirements

• IBAN Standards: International Account Number Specifications

• BIC Directory: Institution Identifier Validation

  Field 25 NoOption: Authorisation

Security authorization code or digital signature between ordering customer and account servicing financial institution.

Fields

authorisation: String

Authorization code or digital signature

Format: 35x - Security token, electronic signature, or agreed authorization code Used for additional security verification between customer and institution

Trait Implementations

impl Clone for Field25NoOption

fn clone(&self) -> Field25NoOption

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Field25NoOption

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for Field25NoOption

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for Field25NoOption

fn eq(&self, other: &Field25NoOption) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for Field25NoOption

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl SwiftField for Field25NoOption

fn parse(value: &str) -> Result<Self>

Parse field value from string representation

fn to_swift_string(&self) -> String

Convert field back to SWIFT string format

fn format_spec() -> &'static str

Get field format specification

fn parse_with_variant( value: &str, _variant: Option<&str>, _field_tag: Option<&str>, ) -> Result<Self>

where Self: Sized,

Parse field value with variant hint for enum fields Default implementation falls back to regular parse

fn valid_variants() -> Option<Vec<&'static str>>

Get valid variant letters for enum fields Returns None for non-enum fields, Some(vec) for enum fields

impl StructuralPartialEq for Field25NoOption