• Ask the Community

  • Capturing failing international payments via API

Although the Bunq API immediately fails for most of the invalid payments, however I assume it may happen that IBAN is valid and everything looks fine in the beginning, but an international transfer might fail much later on the other end in case, for example, the owner's name doesn't match the IBAN. So my questions are:

• Does such payment changes its status as failed later on after it's rejected on the other end (somewhere far abroad) or a separate transaction is created with a positive amount compensating the previous negative amount of the failed payment?
• Is it possible to capture such failing payment via API callbacks? For example, the mutation notification, maybe?
• Since payments do not have any status field within the API messages, how should they be identified among other regular payments?

    I would also like to know how to fetch this status. When looking at the bunq sandbox app they do show the status there (e.g. processing, see screenshot) including an ID and other information, and this information seems to be related to the transferwise-transfer call in the API documentation.

    However, I cannot seem to find where the transferwise-quoteID and itemID parameters from the transferwise-transfer call originate from, nor is there an implementation for this call in the PHP SDK.

    (https://doc.bunq.com/#/transferwise-transfer)

      @Simone-Grey-Leopard#82602 These status values are accessible in the specific objects, the Payment object exists for every mutation and is very generic. If you want the detailed version of each event you are better of using the /user/{userId}/event endpoint which is a list of all Monetary accounts and all types.

      So every Transferwise payment has both a TransferwisePayment object which contains the more detailed statuses and a Payment object.

      @Imantas-Magenta-Panther#82543
      - I think that a regular payment which gets reverted will show up as a new Payment with the same amount. Not 100% sure though since I haven't seen that happen yet myself.
      - If it results in a new Payment than it will definitely cause a Mutation callback event
      - Read above ^ it's a bit tricky at the moment but the most reliable way I've found is either using the events endpoint so you directly see the different specific Objects. Or send API calls to the different types and combine them. So you would get all master-card-actions to get the card payments and then filter out any Payments with a type MASTERCARD for example.

        @Gregory#82611 would this mean that the TransferwisePayment object is not yet present in the PHP SDK, as I'm getting an event with all null values in its EventObject, and there is no property related to transferwise in the EventObject model.

        If so, is there a branch available in the PHP SDK in which the Transferwise models and API endpoints are present? Or would I have to fork and create them myself?

          @Simone-Grey-Leopard#82617 Last I checked the SDKs were up-to-date so if you're on the latest version and it's still not working than it might be a bug

            @Simone-Grey-Leopard#82629 Ah nice find, I'm guessing they have forgotten to publish a new version to Packagist when they created the tag.

              @Simone-Grey-Leopard#82638 I believe sending Transferwise payments isn't possible with the API at all. It probably has to do with the extra steps that are taken in the bunq app which aren't possible through regular API calls.

                @Gregory#82611 thank you for the information. It's very helpful.

                I wonder if there's an exact answer to my question. And probably this is not something that is possible to simulate on sandbox environment. Or is it?

                  4 days later

                  @Gregory#82631 Hi Gregory, so based on this thread I've come to understand that your API doesn't support Transferwise payments, am I correct to conclude that? That's rather serious issue for us as our company has invested an massive amount of effort so far on a software development project which would allow cashback payment via the bunq app using Transferwise integration. Based on the API documentation we were led to believe this would be feasible yet it appears now that it isn't possible to create Transferwise payments via the API for currencies other than Euro's. I assume that his issue will be fixed quickly or can you share the roadmap for when it will be available in the API?

                    @Kevin-Aquamarine-Butterfly-1673631353#84190 First off, I'm not a bunq employee ^

                    But as far as I know sending Transferwise payments through the public API isn't possible and because the app requires you to setup/check for a Transferwise account in the bunq app I don't expect that to change anytime soon.

                      @Gregory Ok wasn't aware you weren't an employee, how do I get in contact with a bunq employee who could possibly tell me if this will be added in the near future?

                        8 days later
                        Write a Reply...