Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CBI File Format (was: Validation error on import XML to my bank) #601

Closed
masetto opened this issue Oct 9, 2020 · 10 comments
Closed

CBI File Format (was: Validation error on import XML to my bank) #601

masetto opened this issue Oct 9, 2020 · 10 comments

Comments

@masetto
Copy link
Contributor

masetto commented Oct 9, 2020

Hi,
I state that this is the first time I create XML file from this module. 😄

XML file starts with this rows:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02 pain.008.001.02.xsd">
  <CstmrDrctDbtInitn>
    <GrpHdr>

When I import to my internet banking (Italian bank) I have this error:
2020-10-09_17h18_23

File pain.008.001.02.xsd does not exist.

Is this a problem of my bank or another one?
Thanks

@bjendres
Copy link
Member

@masetto You can either

  1. talk to your bank and ask which SEPA PAIN flavours they accept, or
  2. try all the formats that CiviSEPA is shipped with, and see if any gets accepted.

@masetto
Copy link
Contributor Author

masetto commented Oct 12, 2020

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

@bjendres
Copy link
Member

bjendres commented Oct 12, 2020

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:

  1. check if the data and the workflows in CiviSEPA can be mapped to that file format. If so:
  2. create a new file format (see e.g. HERE and HERE)
  3. create a PR to add the new file format to CiviSEPA. Alternatively, this could be part of an extension, see e.g. HERE

@bjendres bjendres changed the title Validation error on import XML to my bank CBI File Format (was: Validation error on import XML to my bank) Oct 12, 2020
@masetto
Copy link
Contributor Author

masetto commented Oct 13, 2020

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?

@bjendres
Copy link
Member

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?

@masetto
Copy link
Contributor Author

masetto commented Oct 13, 2020

I'll try it by myself, thanks.

@bjendres
Copy link
Member

@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...

@bjendres bjendres added this to the 1.7 milestone Feb 14, 2022
@masetto
Copy link
Contributor Author

masetto commented Feb 25, 2022

👍 @bjendres, I will continue this shortly

@masetto
Copy link
Contributor Author

masetto commented Mar 30, 2022

@bjendres can you give me some instructions for transferring sepa mandates to CiviCRM. What are the steps to be taken?
Thank you

@bjendres
Copy link
Member

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. )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants