Transactions API missing data with Shopify Installments

hadardo
Visitor
3 0 0

Hi,

When getting data via the shopify_payments/balance/transactions.json endpoint, transactions that were created by the Shopify Installments app don't have a source type (e.g. 'charge', 'adjustment', etc.). Also, the transaction order ID in the response is pointing to the "authorizing" kind transaction and not the "capture" transaction. However, when the gateway is Shopify Payment, there is no missing value in the source type, and the transaction order ID in the response is pointing to the "capture" transaction. 

Is this the expected behavior of the response? Below is a sample response when the gateway is shopify_installments:

 

{
            "id": [id_here],
            "type""charge",
            "test"false,
            "payout_id"[payout_id],
            "payout_status""paid",
            "currency""USD",
            "amount""360.00",
            "fee""18.30",
            "net""341.70",
            "source_id"null,
            "source_type"null, -- No Source_type
            "source_order_id"[order_id],
            "source_order_transaction_id"[order_transaction_id],  -- This is an Order Transaction ID 
            "processed_at""2022-10-17T00:55:06Z"
        }
Replies 3 (3)

Alan
Shopify Staff
129 15 24

Hi @hadardo, happy to look into this further. Could you please share an example X-Request-ID that should be included in the API response header you receive from us when you put a call through? I'd like to take a look at a specific call on my end to see if we can replicate it exactly and share it with my team. 


Hope to hear from you soon - let us know if we can clarify anything on our end! 

Alan | API Support @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog

hadardo
Visitor
3 0 0

Hi @Alan , sorry for the late response.

This is X-Request-ID from a call I just ran: 0e8a7fbd-96c9-40aa-a8ec-de909e1ecaa0.

Thanks,

hadardo
Visitor
3 0 0

Hi @Alan , anu update on this?

Thanks,