• Home
• de.adorsys
• hbci4j-adorsys
• 3.5.25
• source code

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

ci4j-adorsys.3.5.25.source-code.pain.001.003.03.xsd Maven / Gradle / Ivy

	
	
		
			
		
	
	
		
			
			
			
			
		
	
	
		
			
		
	
	
		
			
				
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
			
				
					If used, it is recommended to be used at ‘Payment Information’ level and not at ‘Credit Transfer Transaction Information’ level.
				
			
			
			
				
					It is recommended that this element be specified at ‘Payment Information’ level.
				
			
			
				
					This data element may be present either at ‘Payment Information’ or at ‘Credit Transfer Transaction Information’ level.
				
			
			
			
			
			
			
			
		
	
	
		
			
			
				
					If a Creditor Reference contains a check digit, the receiving bank is not required to validate this.
If the receiving bank validates the check digit and if this validation fails, the bank may continue its processing and send the transaction to the next party in the chain.
RF Creditor Reference may be used (ISO 11649).
				
			
		
	
	
		
			
			
		
	
	
		
			
		
	
	
		
			
			
		
	
	
		
			
			
			
			
		
	
	
		
			
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
			
		
	
	
		
			
			
		
	
	
		
			
			
		
	
	
		
			
			
		
	
	
		
			
			
		
	
	
		
			
		
	
	
		
			
				
				
			
		
	
	
		
			
		
	
	
		
			
		
	
	
		
			
			
			
		
	
	
		
			
			
			
		
	
	
		
			
			
			
			
			
		
	
	
		
			
		
	
	
		
	
	
		
	
	
		
			
			
		
	
	
		
			
		
	
	
		
			
			
		
	
	
		
			
			
		
	
	
		
			
				
				
			
		
	
	
		
			
				
				
			
		
	
	
		
			
				
					
						Either ‘BIC or BEI’ or one
occurrence of ‘Other’ is allowed.
					
				
				
					
						Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ is allowed.
					
				
			
		
	
	
		
			
				
					‘Name’ is limited to 70 characters
in length.
				
			
			
		
	
	
		
			
				
					‘Name’ is limited to 70 characters
in length.
				
			
			
			
		
	
	
		
			
			
		
	
	
		
			
			
				
					Only ‘TRF’ is allowed.
				
			
			
				
					If present and contains ‘true’, batch booking is requested. If present and contains ‘false’, booking per transaction is requested. If element is not present, pre-agreed customer-to-bank conditions apply.
				
			
			
			
			
				
					If used, it is recommended to be used only at ‘Payment Information’ level and not at Credit Transfer Transaction Information’ level.
When Instruction Priority is to be used, ‘Payment Type Information’ must be present at ‘Payment Information’ level. 
				
			
			
			
			
			
			
				
					This data element may be present either at ‘Payment Information’ or at ‘Credit Transfer Transaction Information’ level.
				
			
			
				
					It is recommended that this element be specified at ‘Payment Information’ level.
				
			
			
		
	
	
		
			
		
	
	
		
			
				
					If present, pre-agreed customer-to-bank conditions apply.
				
			
			
			
				
					Depending on the agreement between the Originator and the Originator Bank, ‘Category Purpose’ may be forwarded to the Beneficiary Bank.
				
			
		
	
	
		
			
			
				
					Depending on the agreement between the Originator and the Originator Bank, ‘Category Purpose’ may be forwarded to the Beneficiary Bank.
				
			
		
	
	
		
			
				
				
			
		
	
	
		
			
				
				
			
		
	
	
		
			
			
		
	
	
		
			
			
		
	
	
		
			
				
					Only codes from the ISO 20022 ExternalPurposeCode list are allowed.
				
			
		
	
	
		
			
				
				
			
		
	
	
		
			
		
	
	
		
			
				
					When present, the receiving bank is not obliged to validate the the reference information.