topic Re: Webhook and custom fields, or alternate methods? in Integration and Testing

Webhook and custom fields, or alternate methods?

dbr11 — Mon, 09 Jul 2018 02:12:34 GMT

I am switching from SIM (and Silent URL) to Accepted Host (and Webhooks), using the Authorize hosted payment page. I do not want to use a payment form on our own domain, if possible.

The Silent URL returned many custom fields about the transaction, but it appears that Webhooks doesn't do this. The problem discussed here is exactly my problem: https://community.developer.authorize.net/t5/Integration-and-Testing/quot-Webhook-quot-VS-quot-Silent-Post-quot-and-custom-fields/td-p/61269. But the solution isn't really clear to me. (It was marked 'solved' just based on Brian being available, it seems.)

It sounds like I should use the "transRefId" (or is it "refTransId"?) which I set up, to uniquely identify the transaction, store the details locally in my own db, then when I'm notified via Webhooks that the transaction went thru, use the refId field to locate my db record with the details. Is this right?

Is there really no way to just get the custom fields from the transaction directly?

I'd appreciate some guidance. Thanks.

Re: Webhook and custom fields, or alternate methods?

Anurag — Mon, 09 Jul 2018 06:41:21 GMT

Hi @dbr11

Yes , the custom fields passed during the transactions are not persisted in Authorize.Net systems and therefore cant be returned in the Webhook notifications . The custom fields should be stored on the client side and refID passed in the createTransaction can be used as the lookup key .

You can use the transrefId returned in the getTransactionDetails API https://developer.authorize.net/api/reference/index.html#transaction-reporting-get-transaction-details to lookup for them locally then .

Thanks

Re: Webhook and custom fields, or alternate methods?

johnbrad — Sat, 06 Nov 2021 18:59:18 GMT

I do have the same problem and was able to fix my problem. Thanks for update..

Regards,

BestchairsReviews.com