Axepta BNP Paribas Customer Vault feature enables you to offer your customers a seamless checkout experience. With this feature, customers can securely save their cards for future transactions, making repeat purchases faster and easier thereby improving conversion.

Merchants who are integrated to via Hosted Payment Page or Hosted Forms can enable Customer Vault feature to store buyer's card information on 's secured and compliant infrastructure.

When your customers pay on the card form, they will have the option to save their card details. Saved cards will be available for future purchases with your shop, allowing customers to:

  • Select from their saved cards during checkout.

  • Remove cards at any time.


Get Started

  • Contact to activate this feature, if you are integrated via Hosted Payment Page or Hosted Forms.
  • Once activated, you have to submit the merchantCustomerId in your payment request:
    {
        "customerInfo": {
            "merchantCustomerId": "cus_1234567890abcdef",
            "firstName": "Max",
            "lastName": "Mustermann",
            "email": "customer@example.com",
            "phone": {
                "countryCode": "+49",
                "number": "1236547890"
            }
        }
    }


Payment flow user experience

Registering new customer

Once the feature is activated for your merchant profile and you have passed the merchantCustomerId in the request then the customers see an additional consent checkbox to saved their cards for future purchase. If the customer gives their consent, the customer data and the card details are saved in .

Returning customer

Returning customers (identified by the merchantCustomerId sent in the payment request) view all their saved cards to select from and pay faster.


Managing customers

For every saved customer stores a Customer object and payment method object for each card. One customer can have many payment method objects linked if the customer has stored multiple cards.

You can view and manage customer data via UI or programmatically via our REST API. 

 UI

A new Customers section is available in the . Here you can:

  • View a list of all customers

  • View individual customer details

  • See all cards saved by each customer

  • Update customer details

  • Delete a customer (also deletes their payment methods)

  • Delete a specific payment method.

This gives you full control over customer and payment method records.

REST API 

All customer and payment method management actions are also available via our REST API. This allows you to build your own UI or integrate the functionality into your systems.

Available endpoints


Webhook notifications

Everytime a new customer or a payment method is added in during the payment processing, the information is sent to urls.webhook submitted in the payment request and Customer Vault specific webhook notification endpoint configured for your merchant profile.

Webhook URL 

A new parameter vaultInteraction is sent to the urls.webhook once the payment is completed, informing you about customer's interaction with the Customer Vault on the card form.

Possible values:

ValueDescription
PAYMENT_METHOD_ADDEDWhen a new card is added for a new customer or an existing customer profile.
PAYMENT_METHOD_USED When an existing saved card was used for payment.
NONE Customer doesn't have a vault or an existing customer has paid with a new card but did not save it.

Customer vault webhook notification

The notification sent to Customer vault webhook notification endpoint is the exhaustive information about the payment method data saved in . The information sent is based on type of action the customer performed on the form.

Save a new card

Parameter description

ParameterTypeCNDDescriptionBeschreibung
gatewayCustomerIdstring (32)M

Unique identifer of the customer assigned by

Vom vergebene eindeutige Kennung des Kunden

merchantCustomerIdstring (64)MUnique identifer of the customer assigned by merchantVom Händler vergebene eindeutige Kennung des Kunden
merchantIdstringMMerchant IDHändler-ID
scopestringMScope of the customer vault configured at merchant levelUmfang des auf Händlerebene konfigurierten Kundentresors
paymentMethod.actionenumMDescribes whether the card was created or deleted. For saving a new card the value is "create"Beschreibt, ob die Karte angelegt oder gelöscht wurde. Beim Speichern einer neuen Karte lautet der Wert „create“.
paymentMethod.id string (32)M

Unique ID assigned by for the payment method record

Vom vergebene eindeutige ID für den Datensatz der Zahlungsmethode

paymentMethod.typeenumM

Determines type of payment method. Possible values: card

Bestimmt die Art der Zahlungsmethode. Mögliche Werte: card

paymentMethod.last4Digitsstring (4)MLast 4 digits of the cardLetzte 4 Ziffern der Karte
paymentMethod.pseudoCardNumbernumber (16)CPseudo card numberPseudo-Kartennummer
paymentMethod.cardHolderNamestringMCardholder nameName des Karteninhabers
paymentMethod.brandstringMType of card brand (Visa, Mastercard, etc.)Kartenmarke (Visa, Mastercard usw.)
paymentMethod.expiryDatenumber (6)MExpiry date of the cardAblaufdatum der Karte
paymentMethod.createdAtdatetimestampMCreation date of payment method recordErstellungsdatum des Datensatzes der Zahlungsmethode
paymentMethod.updatedAtdatetimestampMLast updated date of the payment method recordLetztes Aktualisierungsdatum des Datensatzes der Zahlungsmethode
paymentMethod.lastUsedAtdatetimestampMLast used date of the payment method recordLetztes Verwendungsdatum des Datensatzes der Zahlungsmethode


Sample

{
	"gatewayCustomerId": "cu_841b9b1a99fc4f0",
	"merchantCustomerId": "1234567890",
	"merchantId": "demo_store_ecom",
	"scope": "demo_parent",
	"paymentMethod": {
		"action": "create",
		"id": "pm_5555b1a99fe4tg3",
		"type": "card"
		"last4Digits": "4242",
		"pseudoCardNumber": "0132332232424242" 
		"name": "Max Mustermann",
		"brand": "visa",
		"expiryDate": "202506",
		"createdAt": "2023-12-21T12:10:58.087",
		"updatedAt": "2023-12-21T12:10:58.087",
		"lastUsedAt": "2023-12-21T12:10:58.087",
	}
}


Delete an existing card 

This notification is sent when the customer is deleting the card from the payment form.

Parameter description


ParameterTypeCNDDescriptionBeschreibung
gatewayCustomerIdstring (32)M

Unique identifer of the customer assigned by

Vom vergebene eindeutige Kennung des Kunden

merchantCustomerIdstring (64)MUnique identifer of the customer assigned by merchantVom Händler vergebene eindeutige Kennung des Kunden
merchantIdstringMMerchant IDHändler-ID
scopestringMScope of the customer vault configured at merchant levelUmfang des auf Händlerebene konfigurierten Kundentresors
paymentMethod.actionenumMDescribes whether the card was created or deleted. For deleting an existing card the value is "delete".Beschreibt, ob die Karte angelegt oder gelöscht wurde. Zum Löschen einer bestehenden Karte lautet der Wert „delete“.
paymentMethod.id string (32)M

Unique ID assigned by for the payment method record

Vom vergebene eindeutige ID für den Datensatz der Zahlungsmethode

paymentMethod.typeenumM

Determines type of payment method. Possible values: card

Bestimmt die Art der Zahlungsmethode. Mögliche Werte: card


Sample

{
	"gatewayCustomerId": "cu_841b9b1a99fc4f0",
	"merchantCustomerId": "1234567890",
	"merchantId": "demo_store_ecom",
	"scope": "demo_parent",
	"paymentMethod": {
		"action": "delete",
		"id": "pm_5555b1a99fe4tg3",
		"type": "card"
	}
}