Closed masetto closed 2 years ago
@masetto You can either
Hi @bjendres, this is the answer of my bank:
streams starting with the
<Document
tag are NOT accepted by the system, they must be CBI -> CBIBdySDDReq compliant In this case it is NOT enough to modify the start tag, the flow must be created respecting the CBI rules.
What is this standard? Is it different from the ones you have implemented? Thanks
Yes, that seems to be a custom (non-PAIN) file format. I'm not aware of anyone having implemented these CBI file formats for CiviSEPA.
The process of doing this would probably be something like:
Hi @bjendres thank you for your indications. This is an example XML CBI file accepted by my italian bank. Is it a format you have already heard of? I think it is a standard in Italy. Do you think it is useful to develop it in this CiviSEPA extension?
Is it a format you have already heard of? I think it is a standard in Italy.
No, never come across it, sorry.
Do you think it is useful to develop it in this CiviSEPA extension?
If it's an Italian standard, probably. Would you want to do it yourself, or would you want to hire us to do it?
I'll try it by myself, thanks.
@masetto Did you ever manage to create this file format in CiviSEPA? If so, could you create a PR with this? Other people might want to use that, too...
:+1: @bjendres, I will continue this shortly
@bjendres can you give me some instructions for transferring sepa mandates to CiviCRM. What are the steps to be taken? Thank you
You can use the APIv3 using the SepaMandate.createfull
action.
Alternatively, you could use a formprocessor, CiviSEPA offers a couple of actions around SEPA mandates.
(Sorry for the late reply. )
Hi, I state that this is the first time I create XML file from this module. 😄
XML file starts with this rows:
When I import to my internet banking (Italian bank) I have this error:
File
pain.008.001.02.xsd
does not exist.Is this a problem of my bank or another one? Thanks