Register and manage payment agreements for recurring billing.
Get payment agreement status
Returns the current status and details of a payment agreement. The Vipps confirmation URL is only included while the agreement is pending customer confirmation (CREATED or PENDING status).
path Parameters
agreementIdagreementId
Headers
Entur-POSPoint-of-sale identifier.
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Entur-Distribution-ChannelDistribution channel identifier.
Get payment agreement status › Responses
Ok
agreementIdThe unique identifier of the payment agreement.
statusThe current status of the agreement.
productNameName of the product or subscription.
productDescriptionDescription of the product or subscription, shown to the customer in the provider's app.
Base pricing model for a payment agreement.
Base provider-specific data in an agreement response.
Update payment agreement
Updates the mutable parts of a payment agreement, both at the provider and locally.
Every field is optional and at least one must be supplied; omitting a field leaves it unchanged.
pricing is not currently supported — supplying it returns 501. Only FLEXIBLE agreements can be created, and FLEXIBLE pricing has no updatable fields. The pricing field and the underlying FixedPricing/VariablePricing schemas are kept in the spec and reserved for future use; they will be enabled when FIXED and VARIABLE agreement types are introduced.
productName and the provider's merchantAgreementUrl can be updated on FLEXIBLE agreements.
The agreement must be in status PENDING or ACTIVE.
path Parameters
agreementIdagreementId
Headers
Entur-POSPoint-of-sale identifier.
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Entur-Distribution-ChannelDistribution channel identifier.
Update payment agreement › Request Body
productNameName of the product or subscription.
productDescriptionDescription of the product or subscription, shown to the customer in the provider's app.
Pricing model for updating an agreement. Not yet supported — supplying this field returns 501. FLEXIBLE is absent because its amount is set per charge and has nothing to update; FIXED and VARIABLE are reserved for future use.
Base provider-specific data for updating an agreement. Contains only the fields the provider allows changing after the agreement exists — which is why this is a separate schema from AgreementRequestProviderData.
Update payment agreement › Responses
Ok
agreementIdThe unique identifier of the payment agreement.
statusThe current status of the agreement.
productNameName of the product or subscription.
productDescriptionDescription of the product or subscription, shown to the customer in the provider's app.
Base pricing model for a payment agreement.
Base provider-specific data in an agreement response.
Stop payment agreement
Stops a payment agreement, both at the provider and locally. The agreement must be in status PENDING or ACTIVE.
Stopping is irreversible. A stopped agreement cannot be reactivated — resuming service for the customer requires setting up a new agreement. The provider also cancels any outstanding charges on the agreement as part of the stop, so a charge that has not yet been captured will not be captured afterwards.
Any charge on the agreement that has not yet reached the provider is cancelled as part of the stop, and its transaction ends up CANCELLED. That covers the initial charge of an agreement stopped before the customer confirmed it, and a charge on an ACTIVE agreement that had been created but not yet claimed. Neither can make progress once the agreement is stopped.
The endpoint is idempotent: stopping an already STOPPED agreement returns 200 with the unchanged agreement and does not call the provider. An agreement in status CREATED or EXPIRED cannot be stopped and is rejected with 409.
The request has no body.
path Parameters
agreementIdagreementId
Headers
Entur-POSPoint-of-sale identifier.
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Entur-Distribution-ChannelDistribution channel identifier.
Stop payment agreement › Responses
Ok
agreementIdThe unique identifier of the payment agreement.
statusThe current status of the agreement.
productNameName of the product or subscription.
productDescriptionDescription of the product or subscription, shown to the customer in the provider's app.
Base pricing model for a payment agreement.
Base provider-specific data in an agreement response.
Query payment agreements
Returns payment agreements for a given customer across all organisations the caller has access to. Optionally filter by one or more statuses.
query Parameters
customerNumberCustomer number to query agreements for. Required.
statusOptional. Filter by one or more agreement statuses.
Headers
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Query payment agreements › Responses
Ok
agreementIdThe unique identifier of the payment agreement.
statusThe current status of the agreement.
productNameName of the product or subscription.
productDescriptionDescription of the product or subscription, shown to the customer in the provider's app.
Base pricing model for a payment agreement.
Base provider-specific data in an agreement response.
Register a new payment agreement
Registers a payment agreement with the specified provider. For Vipps, this drafts the agreement and returns a confirmation URL to redirect the customer to.
Only FLEXIBLE pricing is currently supported. Supplying FixedPricing or VariablePricing returns 501; those agreement types are reserved for future use.
Headers
Entur-POSPoint-of-sale identifier.
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Entur-Distribution-ChannelDistribution channel identifier.
Register a new payment agreement › Request Body
productNameName of the product or subscription.
customerNumberThe customer number for the agreement.
Base pricing model for a payment agreement.
Base provider-specific data for creating an agreement.
productDescriptionOptional description of the product or subscription, shown to the customer in the provider's app.
Register a new payment agreement › Responses
Created
agreementIdThe unique identifier of the payment agreement.
statusThe current status of the agreement.
productNameName of the product or subscription.
productDescriptionDescription of the product or subscription, shown to the customer in the provider's app.
Base pricing model for a payment agreement.
Base provider-specific data in an agreement response.