2.1.10 • Published 3 years ago

react-paytrail-topfinance v2.1.10

Weekly downloads
3
License
MIT
Repository
github
Last release
3 years ago

npm version NPM

React library and component for creating payments with Paytrail E2 Interface.

Introduction

Screenshot

This library outputs a new <form> HTML element including all the required and optional fields as <input> elements for the E2 interface. Authcode required by Paytrail is calculated dynamically on render.

Payment may be dispatched to the service by submitting the form. Invalid parameters will instantly be caught by the payment service.

⚠️ This is still a work-in-progress. We appreciate your help in testing the logic and fixing any defects found. See how to contribute.

Install

# Yarn
yarn add react-paytrail-e2

# NPM
npm install --save react-paytrail-e2

Usage

The payment form component should be added to your existing order page.

import { Form } from '@paytrail/react-paytrail-e2'

/* order page JSX */

<Form {...props} />

Demo

This project includes a demo React application which you can use to study the on how to pass different properties to this component.

Contributing

The library source code can be found under the src/ directory, and the example app under the example/ directory.

First, install dependencies with yarn. Then invoke a Jest watcher with yarn test:unit to validate your changes.

NOTE: As of yet, there's no automated end-to-end test suite for creating a real payment. Make sure the demo application can create a new payment by click of a button and there are no interface errors.

After you're satisfied with the changes and all tests pass, open a pull request to this project.

Releases

Follow the steps below to release a new version:

NOTE: GitHub Actions pipeline automatically pushes new releases to GitHub package registry when a new release is published. Currently, there's no automatic publishing to NPM registry so it has to be handled manually as below.

  1. Install the np tool by running npm install -g np.
  2. Type np in the project root and select the version bump (patch, minor, or major) according to semantic versioning.
  3. See that all the automated release steps are executed successfully.
  4. Fill the GitHub Releases draft and publish the release notes.
  5. Check that NPM contains the new version.
2.1.10

3 years ago

2.1.91

3 years ago

2.1.9

4 years ago

2.1.8

4 years ago

2.1.7

4 years ago

2.1.6

4 years ago

2.1.5

4 years ago

2.1.4

4 years ago

2.1.3

4 years ago

2.1.2

4 years ago

2.1.1

4 years ago