Go to file
2023-07-05 14:29:29 +03:00
.github Change CODEOWNERS (#22) 2023-04-28 10:29:28 +03:00
apps Revert "Аdd log client info (#23)" (#24) 2023-05-19 18:50:09 +03:00
config Ops 277/optional ip header (#21) 2023-03-31 12:04:45 +05:00
doc CAPI-39: Extract PCI-DSS parts from rbkmoney/erlang_capi/v2 (#1) 2019-05-13 13:38:12 +03:00
.dockerignore TD-125: Add build system (#1) 2022-02-02 15:50:37 +03:00
.editorconfig TD-125: Add build system (#1) 2022-02-02 15:50:37 +03:00
.env TD-367: Drop idempotency guarantees (#18) 2022-08-10 19:48:53 +03:00
.gitignore TD-125: Add build system (#1) 2022-02-02 15:50:37 +03:00
Dockerfile OPS-268: Setups user in Dockerfile (#26) 2023-07-05 14:29:29 +03:00
Dockerfile.dev Use only token in cds.BankCards (#14) 2022-06-01 15:35:16 +03:00
elvis.config TD-125: Add build system (#1) 2022-02-02 15:50:37 +03:00
LICENSE Update file(s) from valitydev/.github 2022-02-22 08:11:46 +00:00
Makefile TD-125: Add build system (#1) 2022-02-02 15:50:37 +03:00
README.md TD-125: Add build system (#1) 2022-02-02 15:50:37 +03:00
rebar.config TD-367: Drop idempotency guarantees (#18) 2022-08-10 19:48:53 +03:00
rebar.lock Bump damsel (#25) 2023-05-22 17:25:30 +07:00

capi-pcidss

PCI DSS part of Common API written in Erlang

Building

To build the project, run the following command:

$ make compile

Running

To enter the Erlang shell with the project running, run the following command:

$ make rebar-shell

Development environment

Run in a docker container

You can run any of the tasks defined in the Makefile from inside of a docker container (defined in Dockerfile.dev) by prefixing the task name with wc-. To successfully build the dev container you need Docker BuildKit enabled. This can be accomplished by either installing docker-buildx locally, or exporting the DOCKER_BUILDKIT=1 environment variable.

Example

  • This command will run the compile task in a docker container:
$ make wc-compile

Documentation

This service implements parts of the swag-payments OpenAPI specification which handle sensitive data. It is designed to be deployed in a PCI DSS compliant zone of the cluster and interacts with other services in this zone (like cds and payment tool providers) to process, store and tokenize various types of payment tools.

@TODO Write more documentation