Hi Din;
Unfortunately, there’s nothing I can do to help with issues with PayWithEther not validating transactions – I don’t have any involvement in the running of that service.
Hopefully you’ll hear back about the support requests you’ve put in soon.
Hi Dinmik
I am also user of this plugin. I am just curious about your result.
I don’t keep anymore messages after this:”Order details submitted to PayWithEther.com for monitoring. txId~” in WC order detail pages. It doesn’t handle callback from PayWithEther at all on my side. Did you modify any parts of this plugin ?
This is code part to create a transaction. I am not sure why they set home_url() as callbackurl.
………………………….
$code = $api_client->post(
‘transaction/create’,
[
‘to’ => get_post_meta( $order_id, ‘payment_address’, true ),
‘callbackUrl’ => home_url(),
‘ethVal’ => $eth_value,
‘reference’ => $tx_ref->get(),
‘dustAmount’ => $dust_amount,
]
);
……………………………
here is request type of the paywithether
……………………………
{
apiKey: <YOUR_API_KEY>,
to: “0x6B6fAAbB987381e5452460449c2c82b85730261E”,
value: 0.1,
dustAmount: 0.00000123,
timeoutInSecs: 1200,
callbackUrl: “http://your-store.com/payment-complete-url”,
reference: “0xabcdef123456”
}
………………………………………
only one field type is differ from both: ‘ethVal’ and ‘value’.
