What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Is it somehow possible to use other formats then JSON in the Glue API? We need to integrate a paymen

U018XELUZS9
U018XELUZS9 Posts: 167 πŸ§‘πŸ»β€πŸš€ - Cadet

Is it somehow possible to use other formats then JSON in the Glue API? We need to integrate a payment provider and they're sending XML in the request body.

Comments

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    Glue API is based on JSON:API, so I would say - no.

  • U018XELUZS9
    U018XELUZS9 Posts: 167 πŸ§‘πŸ»β€πŸš€ - Cadet

    What would be the way to go in scenarios like these?

  • U018XELUZS9
    U018XELUZS9 Posts: 167 πŸ§‘πŸ»β€πŸš€ - Cadet

    We use Spryker as a headless system, we don't have Yves in our project at all

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    Some internal feedback:

    they need separate adapter to communicate with payment provider, we do not use Glue API for such integrations. Some examples would be *Api modules from spryker-eco, e.g.: <https://github.com/spryker-eco/adyen-api>
    
  • U018XELUZS9
    U018XELUZS9 Posts: 167 πŸ§‘πŸ»β€πŸš€ - Cadet

    If I understand this right, this is the oppiite of what we need. We already make http requests to the payment provider from zed, but the payment provider needs to send us requests via http, too. E.g. when a customer paid an invoice order, they send a http request with a paid notification.

  • U01BZ7Q3XRV
    U01BZ7Q3XRV Posts: 148 πŸ§‘πŸ»β€πŸš€ - Cadet

    From what I have heard and experienced (also things like your case), glue API should be used for the communication with a storefront / touchpoint, but is not well suited for system to system (e.g. PSP to Spryker) Communication, these should better be directly connected to Zed where you have a lot of freedom to build the api exactly like you need it

  • U01K43ADW5N
    U01K43ADW5N Posts: 69 πŸ§‘πŸ»β€πŸš€ - Cadet

    We've done something similar with Zed API, it is in beta thought, and I'm not sure if there'll be future development by Spryker for this module

  • Jeremy Fourna
    Jeremy Fourna Lead Product Manager Posts: 130 πŸ§‘πŸ»β€πŸš€ - Cadet
    edited April 2022

    @U018XELUZS9 which Payment Service Provider do you use on your project?

  • U018XELUZS9
    U018XELUZS9 Posts: 167 πŸ§‘πŸ»β€πŸš€ - Cadet

    We use Heidelpay and there is an endpoint in Yves, but the Glue code is missing completely in that module. We have created a Glue endpoint, which communicates with the zed part via the gateway.

    In order to solve that problem for now, we've created an ugly hack: There is now a ConvertXmlToJsonEventDispatcherPlugin which listens on that particular route and converts it to json if it comes in as xml.

  • U018XELUZS9
    U018XELUZS9 Posts: 167 πŸ§‘πŸ»β€πŸš€ - Cadet
    edited April 2022

    One of our former colleagues called it "Heidelpain" btw and I now understand him more and more. We're working on the payment by rates (easyCredit via Heidelpay) integration for months and we're literally waiting for weeks for their support to answer, because of missing documentation. (but that's another story πŸ˜‰)

  • Jeremy Fourna
    Jeremy Fourna Lead Product Manager Posts: 130 πŸ§‘πŸ»β€πŸš€ - Cadet

    Heidelpay will be replaced by Unzer in Spryker. We stopped the improvements on the Heidelpay module