Integration Scenarios
The API reference describes all available parameters and capabilities in a generic and flexible format.
To simplify implementation, this section provides scenario-based guides for specific payment methods and use cases, such as:
- Card payments
- Vipps payments
- Merchant wallet payments
- Alternative payment methods (APMs)
Each scenario highlights:
- Which fields are required
- Which fields are optional
- Which fields are not applicable
- Recommended configuration for that payment method
Use these guides to understand the minimal and recommended request structure for a given payment flow, without interpreting the full generic schema.
Payment Method Scenarios Overview
The table below summarizes what each scenario covers and when to use it.
| Scenario | Typical Use Case | Key Parameters | Special Considerations |
|---|---|---|---|
| Card Payments | Standard ecommerce payments | amountDetails, optional cardSchemeWhitelist, immediateCapture | Supports authorization/capture model, SCA (Strong Customer Authentication) may apply |
| Vipps Payments | Mobile-first Norwegian shoppers | VIPPS.userId, transactionText | App-based confirmation; may require redirect outside embedded flow |
| Invoice (Walley) | Pay-later / invoice payments | invoiceItems, B2C (business-to-consumer) / B2B (business-to-business) data | Requires detailed line items and customer data |
| Coopay (Merchant Wallet) | Closed-loop or branded wallet payments | wspId, claimedUserIds | Wallet-specific identifiers required |
Each scenario provides:
- Minimal required request example
- Optional parameters relevant for the method
- Lifecycle considerations
- Method-specific constraints
Updated 13 days ago
Did this page help you?