Dennis Gorelik

Western Union gives obfuscated error code when I try to pay to my new contractor in Ukraine:
==============
There is a technical problem. Please try again later.

C5344
==============

Phone support has no clue about what C5344 code mean.
They do not even have access to detailed logs.

More advanced technical support (if such thing even exists in Western Union) does not reply to my email for several days already.

What is funny, it looks like I still can send money over Western Union to my other contractors in Ukraine.


Sigh.

I am exploring Payoneer.com
But, apparently, my IQ is not high enough to send money over Payoneer.

These are my options when I try to use "Pay - Make a Payment" option:


According to Payoneer's US phone support:
1) In order to send money from my Payoneer account, I should receive at least $1000 from other clients first.
:-O
My bank account is not good enough for funding my first outgoing payment.

2) There is another option - my money recipient (my contractor in Ukraine) can send me an invoice. In that case I can use my bank account to pay the invoice.
I even could find a YouTube tutorial how to create such Payoneer invoice:
=======
https://www.youtube.com/watch?v=eLloPoLxB4g&t=35s
Go to "Receive" and then "Request a Payment".
=======

The problem is -- there is no "Request a Payment" under "Receive" menu item:



We live in the future (well beyond 2015 where Marty McFly travelled to), but international payment services are still broken...

What would you recommend to send money from the US to Ukraine?

Update: Payoneer saga continues

Starting from 2016-01-20 our old unit tests for PayPal integration functionality do not work anymore.
PayPal changed how their sandbox API works.

----------
https://www.paypal-knowledge.com/infocenter/index?page=content&id=FAQ1766
On January 19-20, 2016
The Sandbox endpoints will be upgraded to new SHA-256, 2048-bit certificates:
...
After June 17, 2016
The Production endpoints will be upgraded to new SHA-256, 2048-bit certificates:
----------


Here's the upgrade instructions from PayPal
===========
https://devblog.paypal.com/paypal-ssl-certificate-changes/
How to Update to Prevent Service Outage
To prepare for these changes, please use the checklist below to ensure everything has been upgraded completely:

Talk to the technical contact or 3rd party partner that you used to create the checkout.
Save the VeriSign G5 Root Trust Anchor in your keystore.
Upgrade your environment to support the SHA-256 signing algorithm.
Perform end-to-end testing of the integration against the Sandbox / Payflow Pilot environment (including Instant Payment Notifications (IPN), Payment Data Transfer (PDT), and Silent Posts).
===========

Why do I need to save certificates into my keystore in order to maintain PayPal integration?
Why cannot they use our standard SSL certificate that we already have installed on our web server?

Why PayPal gives no instructions about how to "Upgrade our environment to support the SHA-256"?

It looks like PayPal architects simply do not care about what their customers (developers) will have to go through in order to maintain their API.

Ironically, revenue from PayPal is less than 10% of our revenue, so maintaining all that complexity associated with PayPal API integration does not make sense.

Update:
Facebook discussion