Create Recurring

Create WIP Charge

Create a new Wallet Initiated Payment ("WIP") charge with the Bancontact network. WIP charges allows Bancontact PAN-based e-commerce transactions to be performed without the need for Strong Customer Authentication. There are two use cases for WIP charges:

  • One click express checkout
  • Recurring payments

If transaction data changes for the subsequent charges, the relevant data can be modified by providing new values. For example, the recurring amount could change monthly.

From November 22, 2026, if a valid card is not found using card.number in the request, the response will be a 409 with type /silverflow/problems/card/invalid.

post/charges/{initialChargeKey}/wip

Request

Path parameters

initialChargeKeystring required

Uniquely identifies a charge.

Example:chg-1e1dAHhgstYTUhlphPzZ

Uniquely identifies the initial charge in the case of a recurring sequence.

Headers

Idempotency-Keystring

This key is used to deduplicate requests that are retried. For more information see the section on Idempotency.

Example:28gKCluIEKp8jVboUyr2

Request body

transactionReferencestring

Unique ID assigned by the merchant or payment service provider for the transaction. Used to identify the transaction.

Example request

{
  "amount": {
    "value": 2599
  },
  "transactionReference": "Dz3dIzE74EfH1HeTInyE"
}

Response

The created charge

keystring required

Uniquely identifies a charge.

clearingMode'auto'
localTransactionDateTimestring iso-8601-date-time required

Date and time of the transaction in the local timezone.

transactionReferencestring

Unique ID assigned by the merchant or payment service provider for the transaction. Used to identify the transaction.

fraudLiability'acquirer' | 'issuer' required

Which party is liable in case of fraud.

createdstring iso-8601-date-time required

The date and time this object was created

lastModifiedstring iso-8601-date-time

The date and time this object was last modified

versioninteger required

The version of this object

Example response

{
  "key": "chg-1e1dAHhgstYTUhlphPzZ",
  "merchantAcceptorRef": {
    "key": "mac-1eOdAHhgstYTUhlphPFf",
    "version": 1
  },
  "amount": {
    "value": 2599
  },
  "status": {
    "authentication": "authenticated",
    "authorization": "approved",
    "clearing": "pending"
  },
  "transactionReference": "Dz3dIzE74EfH1HeTInyE",
  "authorizationIsoFields": {
    "responseCode": "00",
    "responseCodeDescription": "Approved",
    "authorizationCode": "4A4316",
    "systemTraceAuditNumber": "123456",
    "retrievalReferenceNumber": "131608123456"
  },
  "billingAddress": {
    "countryCode": {
      "alpha3": "NLD",
      "alpha2": "NL",
      "numeric": "528"
    },
    "stateOrProvince": "NH",
    "city": "Amsterdam",
    "line1": "Langtown Road",
    "line2": "4200",
    "postalCode": "1234BC"
  },
  "version": 1
}

Changes

No recorded changes to this operation across all 1 revision of this API.