This is a very basic tutorial on dealing with Payeezy, who’s documentation I found sometimes difficult. Some of this guidance, I only found in forum threads and so I document…
Get What You Need
- Merchant Demo account
- Developer Sandbox account
- Merchant Token (demo)
- API secret (sandbox)
- API key (sandbox
Today’s problem dealt with how we view our invoices online. We use an app on the iSeries that creates a PDF and delivers it to a set destination. That destination, in our case is a regular windows server, the files landing in a small site: pdf.mycompany.com.
My initial approach was simple, use the PHP API I have sitting on the iSeries to make a call to the program – passing it the parameters for that specific invoice, await response (which gave me the new created filename) and then redirect to that URL. The method looks something like this:
public async Task<ActionResult> GetInvoiceAsync(int invoice)
GetInvoice getInvoice = new GetInvoice();
var client = new HttpClient();
string fileName = await getInvoice.LoadPDF(invoice);
string url = "http://pdf.mycompany.com/";
url += fileName + ".pdf";
This worked great… 90% of the time, but the other 10% of the time, I clicked too quickly on an invoice and got forwarded to a 404.…
UPDATE (Oct 16, 2018): I now rely on Libman for my front end management. I use its 3 different providers to grab the libraries off of cdnjs, unpkg (supposed to include all npm) and filesystem for local files. See post: Using Libman Providers to Coral Front End Libraries
I love me some Bower, even with the shadow looming over it that it’s time is done. Recently, though, it started to do something weird with just restoring/replacing packages that really began to cause problems with my project (and make for some seriously messy 99* commits).
I can do simple task running, etc but still very much a noob to packaging.
Here was my easy solution for removing Bower and switching over to NPM (and accessing those packages through Views).…
This year I am re-writing my previous payment solution (from PHP to .NET) and first on the project list is credit cards. We are using PayTrace and their client-side encryption as to not have to worry about PCI Compliance.
I’m to the point where I have a Pre-Payment model with all the fields needed to send via JSON. I also have a method to request a token for sending (uses demo username and pass) and a test PEM file I downloaded from the PayTrace site. I also got the webpage scanning credit cards, and I hit submit and.. I get this:
XML Parsing Error: no element found
This is appearing in the console of Inspector in Firefox. Turns out this a generic error Firefox throws out when it’s expending a file but gets nothing.
My path’s are correct, but the “public_key.pem” file is not attaching to my post. The problem? MIME-type.…