Giter Club home page Giter Club logo

Comments (10)

sbidoul avatar sbidoul commented on July 16, 2024

Hi David,

Regarding the BBA structured communication, the l10n_be_iso20022_pain module [1] should solve your issue.

Regarding the XML format, can you send me the files in private mail. I'll have a look.

from bank-payment.

dgouthiere avatar dgouthiere commented on July 16, 2024

Hi Stéphane,
i do it now, thanks for being so fast,
David

from bank-payment.

sbidoul avatar sbidoul commented on July 16, 2024

Regarding the PAIN version 003, you can select it in the Export Type field of the Payment Mode.

from bank-payment.

dgouthiere avatar dgouthiere commented on July 16, 2024

Thx, it is what I did to produce my second file.

from bank-payment.

sbidoul avatar sbidoul commented on July 16, 2024

Regarding the errors in the header, it is surprising because the xml declaration <?xml... as well as the namespace declaration emitted are valid xml and should be accepted.

Can you provide the exact error message provided by your bank?

from bank-payment.

dgouthiere avatar dgouthiere commented on July 16, 2024

ok, i do it via your email to paste images easier

from bank-payment.

dgouthiere avatar dgouthiere commented on July 16, 2024

Le 29/05/2015 17:36, Stéphane Bidoul (ACSONE) a écrit :

Regarding the errors in the header, it is surprising because the xml
declaration |<?xml...| as well as the namespace declaration emitted
are valid xml and should be accepted.

Can you provide the exact error message provided by your bank?


Reply to this email directly or view it on GitHub
#170 (comment).

I cannot capture the message of the bank, but it just pop up :

  • sct_2015-005 => attention aucun schéma n'a été trouvé
  • sct_2015-006 => attention aucun schéma n'a été trouvé
  • sct_2015-004 was rejected because he expected a ciri file - because
    I load a txt file instead of xml (was my fault)

ensuite, j'ai reformaté le header comme mentionné dans les spec febelfin
et c'est passé

bàv,
David


L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com

from bank-payment.

dgouthiere avatar dgouthiere commented on July 16, 2024

Le 29/05/2015 17:36, Stéphane Bidoul (ACSONE) a écrit :

Regarding the errors in the header, it is surprising because the xml
declaration |<?xml...| as well as the namespace declaration emitted
are valid xml and should be accepted.

Can you provide the exact error message provided by your bank?


Reply to this email directly or view it on GitHub
#170 (comment).

Stéphane,

Here is the expected content of the header, from febelfin source.

When you look at the sent files, you will see the differences that I
fixed manually,
Kind regards,
David


L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com

from bank-payment.

sbidoul avatar sbidoul commented on July 16, 2024

Hello @dgouthiere,

I did some additional tests and so far I cannot reproduce the issues you mentioned:

  • the XML header is compliant (the exact format of the XML declaration and namespace attributes in the febelfin spec is just an example and is not relevant, so both the version produced by the module and the version you adapted manually are correct)
  • the structuered communication is correct according to the febelfin spec when you use l10n_be_iso20022_pain from OCA/l10n-belgium

So I'm closing this issue. If you feel there is still something incorrect, do not hesitate to reopen and provide additional information.

from bank-payment.

dgouthiere avatar dgouthiere commented on July 16, 2024

Le 15/06/2015 12:08, Stéphane Bidoul (ACSONE) a écrit :

Hello @dgouthiere https://github.com/dgouthiere,

I did some additional tests and so far I cannot reproduce the issues
you mentioned:

  • the XML header is compliant (the exact format of the XML
    declaration and namespace attributes in the febelfin spec is just
    an example and is not relevant, so both the version produced by
    the module and the version you adapted manually are correct)
  • the structuered communication is correct according to the febelfin
    spec when you use l10n_be_iso20022_pain from OCA/l10n-belgium

So I'm closing this issue. If you feel there is still something
incorrect, do not hesitate to reopen and provide additional information.


Reply to this email directly or view it on GitHub
#170 (comment).

Hi Stéphane,

Thanks for feed-back !
Next week I will work on reinstalling my payment modules + the patch and
will remake a real test with the bank.

I will keep you posted

Kind regards,
David


L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com

from bank-payment.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.