The idea of is to store customer data like credit card data, billing / shipping address in a secure way within
and to re-use these data based on CustomerId.
The Customer Data Storage (CDS) refers to a Scope which can be used to share the same CDS data with multiple of your MerchantIds.
After Customer Data Storage has been activated for your MerchantId within :
We can setup a notification URL provided by you. For each change of the Customer Data Storage (CDS) Data you will get a notification message containing the CustomerReferenceId. This can then be used to request these data from CDS.
Currently storage of credit card data is supported, only. Support for other payment data and other consumer data may be added in a later stage.
The Customer Data Storage is addressed via CustomerId and is embedded into payment processing.
With activation of Customer Data Storage (CDS) by you will need to provide an URL to receive notifications for CDS updates. The data will be sent as POST-request and data are part of request-body.
Notifications for CDS-updates are not encrypted, because they do not contain sensitive data.
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
|
CDS inquiries within return stored CDS data for a given CustomerId or CustomerReferenceId.
|
|
Parameters for CDS inquiries via socket connections
|
Response parameters in the case of CDS inquiries via socket connections
|
|
CDS inquiries within can delete stored CDS data for a given CustomerId or CustomerReferenceId.
|
|
Parameters for CDS inquiries via socket connections
|
Response parameters in the case of CDS inquiries via socket connections
|
Currently these templates are supporting
Template names:
|