As a payment method Part Payment gives the consumer the opportunity to pay even larger orders in parts within a longer time period, if they don't want to or can't pay for the entire order at the time of placing the order. By letting the consumers know about the opportunity to use Part Payment as a payment method, you can increase both the number of customers and the average value of an order.
By relieving any uncertainty concerning the use of Part Payment as a payment method in the web store and in the early stages of the order process, you can strengthen the consumer's confidence and they can get acquainted with the products and enjoy shopping more freely.
Svea Payments offers the web store
Banner images presenting Part Payment
An example of part payment installments for the product page (embed)
Material based on which the web store can create a page presenting Part Payment in their web store. The presentation page includes a calculator with which the consumer can calculate payment plans and installments for different sums of their own choosing. Additionally, the web store can can place products on the page and payment plan examples will be fetched from Svea Payments system.
The examples of payment plans and installments are fetched from Svea Payments server and are real.
Svea Payments supports following functions for recurring payments with credit cards:
Registering a credit card for recurring payments (= saving / tokenizing card for later use)
Registering a credit card while doing a payment
Debiting a credit card without payer's intervention (no-click payments)
Querying information of a registered card
Querying information of a payment done with registered card
All refunding and other functions that are applicable to payments done via Svea Payments
For more information, please contact our sales: firstname.lastname@example.org
When everything goes as planned the payments are confirmed by the payer's browser when they return to the webstore; the payer is transferred by a redirect to the pmt_okreturn -URL that was in the payment process initiation.
Sometimes the payer does not return to the webstore. Loss of connection could be one cause for such event. Sometimes there could be other reasons for the payment confirmation to fail. That's why we recommend that every web store should integrate our Payment Status Query API so the web store platform can query the status of the payment if needed.
Svea Payments also has a callback function in which we call the pmt_okreturn -URL server to server. This is an optional service that is off by default. When the service is enabled, Svea Payments server will call the pmt_okreturn -URL when Svea Payments learns that the payment was made. That is, either when the payer returns from whichever payment method they chose, or when we find the money on our bank account, or when we do a status query to where the payer chose to pay.
When callback is enabled there will always be two calls to the ok url in the normal scenario where the payer returns to the web store succesfully after paying. The first one should be by the payer's browser and within 2 minutes the second call is made by the Svea Payments server. If the payer experiences connection problems the first call could be from Svea Payments server. In the case where the second call is by the payer's browser it would be good for the web store to show a message that indicates that the order was already marked as paid and not just display some generic error message.
Any HTTP status code other than 500-505 will be considered as success. In case of 500-505 responses, Svea Payments will retry the callback ten times during the following day or so.
For the callback to work the following conditions must be met:
The web store must be able to handle sessionless call to the ok url.
The first call to the ok url permanently marks the payment status as success. That is, nothing should change the payment status to cancel or error or anything other than success.
Also, the web store must not consider multiple calls to the ok url as multiple payments.
For more information please contact our technical support: email@example.com