Miscellaneous

It is possible to query for information about an order. The results of such a query depends on how much information is stored in the InfoSystems database, and the querying possibilities at the provider. To query for information the only required information is the original order reference that was returned when doing the request to StartPayment or PerformAgreementPayment.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://tech.infosoft.no/schemas/2012/08">
  <soapenv:Header/>
  <soapenv:Body>
    <ns:QueryPaymentRequest>
      <ns:OrderReference>42</ns:OrderReference>
    </ns:QueryPaymentRequest>
  </soapenv:Body>
</soapenv:Envelope>

It is possibly to use the InfoSystems payment as a general abstraction layer or standalone payment provider, there are no requirements for a payment to be associated with a subscription. This might be relevant for various fringe activities where credit card payments are need, and some of the provider complexities can be hidden away.

In cases where a customer is known to exist from before, it is even possible to use the agreement of that customer so he or she won't have to enter credit card information anew. It will also make it possible to track/report on the payment in InfoSystems using any reporting tools you already have.

A standalone payment is carried out using StartPayment, CompletePayment and possibly CapturePayment, in much the same way as when ordering a new subscription but without the additional steps related to the subscription.

Note that if the payments are two-phased, you cannot rely on the system to execute the capture for you, as it has no knowledge on how to do it. For some providers it is possible to capture the amount in small increments, allowing you to separate shipments and payments.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://tech.infosoft.no/schemas/2012/08">
   <soapenv:Header/>
   <soapenv:Body>
      <ns:CapturePaymentRequest>
         <ns:OrderReference>42</ns:OrderReference>
         <ns:Amount>4200</ns:Amount>
      </ns:CapturePaymentRequest>
   </soapenv:Body>
</soapenv:Envelope>

"00"

The operation was successful

"17"

Unknown product code

"99"

An unknown error occured

"226"

Invalid term for product

Other Resources