PCI Vault Forms vs Simple PAY.JP Payment

Securely capture payment card data from your site using PCI Vault. PCI Vault is a vendor neutral PCI DSS compliant environment designed to reduce your PCI compliance scope to a SAQ by using credit card tokenization. Data captured with this plugin will be sent to PCI Vault’s DSS compliant environment directly, and will not be present on your own server. This allows you to securely capture and tokenize credit card data without being PCI DSS compliant. How it Works The plugin comes with a short code that loads PCI Vault’s own Payment Card Data (PCD) form, and makes all the necessary requests to the PCI Vault API in order to get the form working. You can read more on the API side of things here. Take note that this includes 2 paid API requests: 1 when the form loads, and 1 when the data is being sent to PCI Vault. To use this plugin, add your authorisation details, and the user/passphrase for a key, in the PCI Vault Options menu. You can then load the capture form anywhere in your site by using the pcivault_capture shortcode. Shortcode Attributes All valid short code attributes are imported directly into the javascript that renders the form. The security of these attributes are the responsibility of the site, and not PCI Vault. Every attribute must be a valid Javascript expression. We recommend to use function calls that return the values you want the attributes to have, this will grant extra flexibility and avoid issues with WordPress’s sanitisation. The attribute options are: success_callback: A JS function to call if the card was successfully stored. error_callback: A JS function to call if the card was not successfully stored. extra_data: Extra data to store along with the card, must be a valid JS object. This is where using a JS function call really helps. show_card: A true/false value on whether or not to show the card on the form. disable_luhn: A true/false value on whether to disable validation on all form fields. force_keypad: A true/false value on whether to force the user to use a randomised on-screen keypad for entering card numbers. This helps to protect you from key-loggers. field_options: A configuration object for specifying which of the form fields to show or validate. For more information on these fields, please check the documentation for PCI Vault’s Payment Card Data (PCD) form. PCI Vault All of the magic behind this plugin happens on PCI Vault’s environment. This plugin sends an authenticated request to PCI Vault, retrieving a unique capturing endpoint. This request includes your authentication details, and the key/passphrase pair specified in the PCI Vault Options menu. This plugin also loads a hosted PCD form from PCI Vault. You need to be a customer of PCI Vault for this plugin to work. You can view our pricing and register an account. Also have a look at our Terms of Service and our Privacy Policy.

This plugin provides payment form by PAY.JP with simple shortcode. Note: The supported currency is only JPY so far. Example of Shortcode: [simple-payjp-payment amount=50 form-id="id-string" name='no' result-ok="https://example.tokyo/?page_id=7" result-ng="https://example.tokyo/?page_id=8" ] amount (mandatory*): price in JPY plan-id (mandatory*): subscription plan ID form-id (mandatory): any ID of the form name: show/hide name field (‘yes’ => show (default), ‘no’ => hide) result-ok: page url to redirect after payment succeeded if you want to customize success message result-ng: page url to redirect after payment failed if you want to customize failure message prorate: disabled/enabled prorated for subscription payment (‘no’ => not prorated (default), ‘yes’ => prorated) (*) ‘amount’ is mandatory for single payment. ‘plan-id’ is mandatory for subscription payment. ‘amount’ and ‘plan-id’ should be exclusive. You can confirm these information of each payments in descripton property of Charge record on PAY.JP admin panel. Only one shoutcode can be placed in a page. API Action hook simplepayjppayment_result_ok: called after payment succeeded simplepayjppayment_result_ng: called after payment failed Localization English (default) – always included Japanese – always included Technical Details How to use is summalized in the following page: WordPressプラグイン Simple PAY.JP Payment About the 3D Secure Feature Depending on the default settings of the browser or user-specific configurations, the pop-up blocking feature might be enabled. If 3D Secure authentication is attempted in a subwindow format under such conditions, the subwindow launch may be blocked, making authentication impossible. Disclaimer Thank you for using the “Simple PAY.JP Payment” plugin (hereinafter referred to as “this plugin”). Please carefully read the following disclaimer before using this plugin. By using this plugin, you agree to the terms outlined below. User Responsibility This plugin is provided “as is” without warranties of any kind, either express or implied, including, but not limited to, implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The developer assumes no responsibility for any issues or damages arising from the use of this plugin. Users are responsible for configuring and operating the plugin at their own risk. Responsibility for Financial Transactions The developer assumes no responsibility for any financial transactions conducted using this plugin. It is the user’s sole responsibility to verify the accuracy and security of transactions. We strongly recommend seeking legal advice as needed. Data Protection and Security While this plugin is designed with data protection and security in mind, complete safety cannot be guaranteed. Users are advised to implement appropriate security measures, such as installing SSL certificates and performing regular backups. Support and Updates This plugin is subject to ongoing improvement and may be updated or modified without prior notice. However, the developer does not guarantee compatibility with specific environments or the functionality of the plugin after updates. Use of Third-Party Services This plugin may utilize third-party payment services or APIs. The developer is not responsible for any issues arising from these services, including service interruptions, errors, or security risks. Please review the terms and conditions of any third-party services you use in conjunction with this plugin.