xml credit card interface

[Jose Lerebours]

On 10/05/2016 12:04 PM, Fairlight via Filepro-list wrote:
> On Wed, Oct 05, 2016 at 11:26:21AM -0400, Jose Lerebours via Filepro-list thus spoke:
>> If it is XML, you must be referring to SOAP/WSDL ... Can you provide
>> a link to their API page?
> Says who?
>
> You can pass entire XML documents inside a normal URL-encoded field.  For
> that matter, you can also use XML with REST, although it's not as
> commonplace as JSON.

Yeah, go ahead and tell me again about how much you understand about the 
things you read on your spare time.  Fact is that if you are processing 
credit cards on line and XML is involved, there is a greater than 98% 
chance that SOAP/WSDL is involved.

This is a fact - you do not have to like it - agree with it or even 
support it ... Just like PHP is used in over 50% of the WWW today.

>> I use Basys and I am successfully processing with them using SOAP
>> and PHP via their secured WSDL access.  Listen, I will write the
> "[V]ia their secured WSDL access"?  Seriously?
>
> https://en.wikipedia.org/wiki/Web_Services_Description_Language
>
> Nothing about accessing the WSDL in a secure fashion guarantees a thing
> about the security of the web service itself.  What's more, you're not
> processing with them -via the WSDL-.  You're processing with them via the
> web service described -by- the WSDL.
>
> And again...sloppy.

My bad - I thought that https meant secured and since it is done using 
https://~.wsdl I figured that it is a secured WSDL access.

But hey, one never knows.  Perhaps, I keep posting here so that you keep 
picking apart and so I'll get a free education.

>
>> code for you for FREE if you register with Basys as my "Customer"
>> ... I get paid from them since I am an Account Manager of sort ...
> Because this sounds like something -I'd- trust doing...  /sarcasm
>
> mark->
I do not need your approval in any shape or form - For as long as those 
making the decisions, confirming the certification and signing the 
checks are happy ...