In case of both service types, direct payment services and escrow payment services, the payment assignment is created using Payment API. After the buyer has confirmed the online bank payment or card payment or has approved an invoicing contract, Svea Payments redirects the buyer back to webstore with appropriate response information. The response is sent also in case of deliberate cancellations and errors. The webstore determines a separate return address (URL) for each scenario: ok, cancel and error.
Skip to contents in this page
Payment Status Query
It is certainly possible that the webstore never receives a response to new payment request. That is, the buyer never returns to any of the return addresses of webstore. This could for example occur in case of Internet connection shortage. These payment request should not be considered cancelled or erroneous. The actual payment status of every this kind of payment request or order (to which the webstore has not received an OK response) should be queried from Svea Payments through Payment Status Query API. If necessary, Svea Payments verifies the payment status from the bank, card payment handler or credit provider. The query should be done earliest at least one hour after last buyer action to achieve the most reliable answer to the question whether buyer has paid the order. See full details from Payment Status Query API description.
Refunds and Cancellations
Below one can see a couple of examples of return and cancellation processes.
If there's a need to make a refund to buyer after the payment has already been settled to the vendor one needs to make a refund after settlement. Refunds after settlements can be made to card payments, in certain cases for orders made with invoice, part payment or B2B invoice, and if separately agreed, to online bank payments. Usually, for orders paid with online bank credentials, the seller makes after settlement refunds directly to the payer. The seller can make refunds after settlements in Extranet by using its refund tools or by using the technical interface.
Handling of response messages
Fields that are submitted from webstore to Svea Payments and back, may not change while they are being handled by Svea Payments. Fields submitted back must be compared against the original fields.
Fields that are generated by Svea Payments and submitted as part of the response, must be formally validated, as defined in the interface specification and in Hash Generation chapter.
Hash must be calculated from the data in response and that hash must be compared with the pmt_hash field of the response. Calculated value may not differ from the one in response.
If all the checks above are successful, the response can be handled as a valid one.