Invoice to ePayment
Below, you can find comparison between the existing MobilePay Invoice API and the new ePayment API replacing MobilePay Invoice.
Visit our Recommended flows section to see the recommended flow for invoice.
info
If you didn't make the integration yourself, talk with your partner.
Authentication and management
We will have a joint authentication solution across our API platform and introduce a Management API to retrieve merchant data. Read more here.
Input formats
MobilePay invoice | Vipps MobilePay ePayment |
---|---|
InvoiceIssuer | Merchant-Serial-Number (see HTTP headers) |
ConsumerAlias {Alias, AliasType} | Customer {Alias} (Example: 4512345678) |
TotalAmount | amount {currency, value (øre)} |
InvoiceNumber / PaymentReference | reference / paymentDescription |
DueDate | expiresAt (Must be between 10 minutes and 28 days. Example: 2023-02-26T17:32:28 ) |
(InvoiceLink ) RedirectUrl | returnUrl (The URL the user is redirected to after the payment session). |
Comment | N/A |
ConsumerAddressLines [] | N/A |
DeliveryAddressLines [] | N/A |
ConsumerName | N/A |
TotalVATAmount | N/A |
IssueDate | N/A |
OrderDate | N/A |
OrderDate | N/A |
DeliveryDate | N/A |
MerchantContactName | N/A |
MerchantOrderNumber | N/A |
BuyerOrderNumber | N/A |
InvoiceUrl + InvoiceArticles [] | See: Order Management API |
N/A | paymentDescription |
N/A | profile (scope ) |
N/A | paymentMethod (WALLET or CARD . CARD → WEB_REDIRECT) |
N/A | userFlow (PUSH_MESSAGE , NATIVE_REDIRECT , WEB_REDIRECT , QR ) |
N/A | qrFormat {format, size} (only applicable when userFlow is set to QR ) |
N/A | customerInteraction (CUSTOMER_PRESENT , CUSTOMER_NOT_PRESENT ) |
N/A | industryData (In special cases only: Additional compliance data related to the transaction) |