Revolut Business Api failure on transfer and payment endpoints - php

I'm trying to integrate Revolut Business Api into our system. Mainly it will handle only payments to external (non-revolut) accounts.
Working in php and using Laravel.
I’m using the sandbox environment and the authorization process is working well, also checking our own accounts (different currencies) and creating and editing counterparties are working as expected.
During the development I and ran into a problem and I couldnt find any information online or in any community pages.
Any other endpoint (besides the above mentioned) that I’m calling is giving back an error 500 with the following error message
e.g: {"message":"Oops! An error occurred while processing your request. It has been logged for further investigation. Error Id: xxxxxxxxxxxxx”}
For testing purposes I send it payloads with bad data, and the response is working as expected pointing out the problematic data.
e.g: wrong currency transfer from specific account, or negative figure in the amount field, etc.
But whenever I send in a correct data (I believe it is correct) it responses with the above mentioned 500 error.
I do believe that the problem is on my end and I’m doing something in not the specific way.
Is anyone ran into the same situation?
Thank you
Tamas

Related

Docusign Connect and PCI compliance?

Ok, so I have setup a Docusign Connect to a 3rd party application (Infusionsoft) and have it working great.
They don't natively work together, so I created a php script that reads the tabs in the docusign envelope, and passes it to Infusionsoft, along with a copy of the completed envelope itself.
Now I would like to pass payment info through this as well, as one of the document templates I have in Docusign is a billing agreement. I have done a test run of this with dummy info and I am able to do this well, BUT, I now have to be concerned with PCI compliance on this, right?
I have a dedicated server with a domain that has an SSL certificate which is hosting the php script, which does not store any information. It just passes the docusign info (gathered by using the docusign connect) and then formats it so it can be accepted by Infusionsoft.
I am a novice programmer, and pretty ignorant regarding knowledge behind encrypting data or securing a connection. The fact that Docusign passes the info through an XML file seems to be not ideal for handling sensitive data (at least I would imagine), and that is something that is out of my control.
So what I am asking is would it be possible to securely transmit payment info (credit card or bank account) through a Docusign connect connection in the type of setup I have? If so, how would I approach it? I am open to hiring a programmer if needed or getting a different server setup if it was necessary.
I can do this without adding the payment info to the template, and just adding it afterwards directly into Infusionsoft to limit my liability, but it would be so much easier if I could do it directly through Docusign Connect as it would automate the entire sign up process.
Well Comodo's test turned up a bunch of holes and warnings, with a detailed report of what to fix. I took that in turn to Hostgator support, who went ahead and made the appropriate changes to fix the holes. The also reported that their were a bunch of false positives with supporting documentation.
So I have to do another test to verify that everything was closed up and report the false positives. But other than that it seems like it should all be cleared up.
I also spoke with Docusign Support over the phone about this, and they confirmed other companies are doing what I am doing as well, which was reassuring.
So in short, use Comodos online scan tool to see what holes you have. Then contact your hosting company to fix the holes. Not a great answer, but I suppose better than nothing.

Bigcommerce - Developing an application in PHP - Webhooks

This is my very first application I'm developing for an internal business requirement and I'm needing some help getting started.
So far I have found their documentation to be quite low in terms of standards but with a lot of Googling and research, I've managed to get a successful request producing an Access Token.
I have used Composer to download Guzzle and create a little code that listens to a GET request and I POST some details up and received the token. Great!
What now? It looks like I need to register a web hook but first I want to start with listing hooks - just to get a feel for what I need to do next.
I'm looking to retrieve order details each time a order is placed.
Questions:
I have a oauth.php file hosted on a SSL host which is called when I install a app. This gives me a token. Do I straight after receiving the token, register the web hook?
If that is a yes, do I now create a webhook.php file which listens for orders placed in real time?
If that is a yes, do I need to run the same code I have in oauth, to check if I'm allowed and if so, listen to the call and process?
Once you have an access token, you can create/list webhooks at any time. According to the sparse documentation, your access token will expire in 30-60 days, so you will need to eventually renew it.
Once you have created the webhook you will need a script in place to receive the incoming data from BigCommerce. If the webhook receives an HTTP code other than 200 from the script, it will attempt to repeat the request with a delay, and after a number of failures will eventually mark the hook as inactive.
You don't need any oauth related code on the script that is being triggered by webhooks. If you do want some form of authentication to verify the source of the data, look into the documentation on sending custom headers with the webhook requests. When the webhook triggers it will send a JSON object that contains the scope and ID of the resource that was changed.
It should be noted that while you need an HTTPS URL for both the oauth process and the webhook triggers, the webhook triggers will not work unless your SSL has all intermediate certificates loaded. You can get through the OAuth process without this, but the hooks will simply not work, to the extent of not even hitting your servers access logs.

how php handles multiple http requests

I am developing a project which is related to credit card processing. Developing a server in php which will accept card number from another php page(this php page gives card number to php server from database).
The problem is that there may be multiple users who will access my php page at the same time and will send the card number to server. How can I handle multiple requests?
I googled and found that curl does such things. But didn't get detailed information about it. Can anybody help me?

WePay payment gateway integration in PHP

I want to integrate WePay payment gateway for my site. I have download SDK from www.wepay.com and integrate it as the API tutorial given in WePay, i am done till account creation and API call, but stuck in checkout page. My checkout page goes blank, i am not able to find what the actual problem is?
If anybody is familiar with WePay payment gateway then, please help me out from this problem.
I would suggest you to start with trying to get a decent error message. You can check what they mean here. Use the developer tools like the network tab in Chrome, or Firebug to see how the requests are send and what errors are sending back. An API call is based on an HTTP request so is easy to monitor. It can be that the user is not good or the token or a million other things.

Apple push notification with an enterprise application

we have developed an application that use push notifications by following the very good guide created by David Mytton.
The push service worked great on the development profile. But now that it is finished we have changed to the customers distribution profile. The application is an in-house application using an Enterprise account.
We have changed the certificate on the server and we have changed to the production url as specified in the tutorial. We have also replaced the profile used when building the application and installed it to the tester iPhone. Everything seems to work on the server, and no error messages is returned but the push is never recieved on the iPhone. We are pretty clueless right now and don't know where to start debugging on this. We have checked that the tokenId is updated after replacing the profile.
Has anyone any experience in this and might know what's wrong or where to start debugging? Thanks!
I have no idea what was wrong here but i finally got it to work..
After hours of debugging without results i threw in the towel and created a new developer certificate, app id, push sertificate and distribution profile. I cleaned the project added the new profile and replaced all files on server.
And it worked! No problems at all... Sometimes i hate being an iPhone/Apple developer :\
A few things that you could try:
Make sure your phone is plugged in to a power source (sometimes not having this causes delayed notifications).
Use the following PHP library:
http://code.google.com/p/php-apns/
This allows you to debug the communication with the server and see where the error occurs. Specifically it allows you to debug if your token id is incorrect.
You could try using an incorrect token id on the server and see the behavior. Compare this with using the correct token id.
Any in-house distribution profile gives out a same tokenID, how ever
this tokenID varies across different devices.
Other only issue could be only with the ProductionURL.
I have also notices that the push notification reception is delayed sometimes, mostly when used with production URL.
Hope this helps.

Categories