Paymentgateway web Iframe support

This applies to : https://gattinn.pei.is and https://gattin.greidslumidlun.is

When using an Iframe solution in a payment gateway there is a certain flow that must be used

How it works

1. Post an order → https://api.pei.is/docs/ui/index#!/Orders/Orders_SubmitOrder

   1. More detail about posting order is here

   2. The key detail that must be set correctly when using IFrame is SuccessReturnUrl and CancelReturnUrl

2. Open the payment gateway web in iframe mode on your webpage.

3. The payment gateway web will handle all 3DS verification so that happens all inside the Iframe.

4. When the user has made a payment an event from the payment gateway webpage in the Iframe is sent to the parent page.

   1. This event contains information about if the payment was successful or failed and has the error code from Pei regarding and will include additional code and message from acquired if a credit card payment is made.

   2. Event example of a successful credit card payment event

      • { "statusCode" : 200 "message":"Payment Completed", "isPaymentCompleted" : true, "reference" : "some reference data from merchant", "orderInfo" : { "orderId": "Muixxxdd3qe14dQBAp5wOYTE8kWiVIBjg", "buyer": { "name": "Buyer name", "ssn": "3000493993", "email": "someemail@pei.is", "mobileNumber": "9999999" }, "merchantId": 4, "successReturnUrl": "https://gattinstaging.greidslumidlun.is/iframe/completed?ref=123", "cancelReturnUrl": "https://gattinstaging.greidslumidlun.is/iframe?ref=123", "amount": 7250.0, "isConfirmed": true, "paymentMethod": 1, "items": [ { "id": 1641944, "name": "Gjöf", "quantity": 1.0, "unitPrice": 7250.0, "amount": 7250.0, } ], "cardActionResult": { "acquirerStatusCode": "00-I", "acquirerMessage": "Authorized." }, "confirmationDate": "2022-12-01T18:55:23.233", "mandateId": null, "maskedCard": "XXXX-XXXX-XXXX-6699", "cardType": "Mastercard", "authorizationCode": "815455 } }

   3. Event example of a failed credit card payment event

      • { "statusCode" : 1002 "message":"Buyer does not have enough .....", "paymentCompleted" : false, "reference" : "some reference data from merchant", "orderInfo" : { details about the order ...... } }

5. When the payment is successful and postback (webhook) message is sent to the merchant if defined in the order.

   1. Example of postback message

      1. { "orderId": "JqOuxhTtxJaxsxmXQ3JKIVjh2Jg23F5v", "purchaseId": 13593391, "mandateId": "bxex1d67c44e4f1fa03b8cbb97dca85f" }

Diagram of the flow

New Return and Refund response in OrderAPI

We added card acquirer transaction response both on success and failure. Just note that the “cardActionResult” section will only appear in the failure response when the cause of the error is transaction failure or something related to the acquirer action.

The return command is used to fully refund the credit card payment of an order.

See more information with this link https://api.pei.is/docs/ui/index#!/Orders/OrdersV1_Return

Responses:

200, Success:

400, Failure

The refund command is used for a partial refund of the credit card payment of an order.

See more information with this link https://api.pei.is/docs/ui/index#!/Orders/OrdersV1_Refund

Responses:

200, Success:

400, Failure

Returning information about the order, “OrderAPI” “GET Orders”

A few things have been added to the order to provide more information about the order.

See more information on this link

Example of response

No retry policy from the ValitorPay gateway

The system has been implemented to take into account and handle the No retry policy from ValitorPay.
More information about that can be found on ValitorPay web site

Added support for treating Payment slips in the name of the Merchant.

Today almost every payment slip is created in Geiðslumiðlun name and that can be confusing for the buyer to see what he will be paying for and from what merchant.

Now there has been added support to use the merchant B2B bank account to create the payment slip in their name but still use the Greidslumidlun payment gateway.