#playful_possum_11773

1 messages · Page 1 of 1 (latest)

summer spruceBOT
teal frost
#

Hi there!

jade spruce
#

Hello Soma

teal frost
#

can you share the REfund ID (re_xxx) with this issue?

jade spruce
#

Sure

#

This was the response we received

#

This was the response we received in Celigo;
{
"id": "re_3OJzLoGMGczsHUNw14QUXnTS",
"object": "refund",
"amount": 2178,
"balance_transaction": "txn_3OJzLoGMGczsHUNw1EDyyVTD",
"charge": "ch_3OJzLoGMGczsHUNw1I6q8MyT",
"created": 1701785536,
"currency": "usd",
"metadata": {},
"payment_intent": "pi_3OJzLoGMGczsHUNw1tAyhAkz",
"reason": "duplicate",
"receipt_number": null,
"source_transfer_reversal": null,
"status": "succeeded",
"transfer_reversal": null
}

#

You can find the refund ID there

#

and you can see that meta data field is empty

teal frost
#

I know nothing about Celigo. but the Refund you shared does have a metadata property set.

#

note that when the Refund was created, there was no metadata set. so it was added later.

jade spruce
#

Yeah. We received this credit not ID in the response as a Meta data previously. But suddenly this issue came and now we dont receive it

#

Do you have any idea why it happened

teal frost
#

This was the response we received
it's the response to what exactly? the creating request of the refund, a webhook event, something else?

jade spruce
#

POST request to celigo .Celigo act as a middleware and take those data and pass it into another system

teal frost
#

again I know nothing about Celigo. so not sure I can help. maybe try asking their support team?