WordPress.org
Get WordPress

Plugin Directory

Changeset 1752886


Ignore:
Timestamp:
10/26/2017 03:25:19 AM (8 years ago)
Author:
simonunderwood
Message:

Version 1.0.2 - updated screenshot and description

Location:
assembly-payments-gateways
Files:
2 added
2 deleted
1 edited

Legend:

Unmodified
Added
Removed

  • assembly-payments-gateways/trunk/readme.txt

    r1752310 r1752886  
    5252### Secure payment with CVV/CVC test
    5353
    54 ### Customers need to insert their card verification number (CVV) to check the validity of their card and reject any failure. This protects merchant from fake cards and fraudsters.
     54Customers need to insert their card verification number (CVV) to check the validity of their card and reject any failure. This protects merchant from fake cards and fraudsters.
    5555
    5656### Credit card/Debit Card Payment
    … …  
    6969
    7070**Pricing for Assembly Payment starts at 2.9% plus 30c for credit card payments (1% for ACH Debit). For more pricing information, see** [**here**](https://assemblypayments.com/pricing/) **.**
    71 
    72 A few notes about the sections above:
    73 
    74 *   "Contributors" is a comma separated list of wordpress.org usernames
    75 *   "Tags" is a comma separated list of tags that apply to the plugin
    76 *   "Requires at least" is the lowest version that the plugin will work on
    77 *   "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on
    78 higher versions... this is just the highest one you've verified.
    79 *   Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for
    80 stable.
    81 
    82     Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so
    83 if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used
    84 for displaying information about the plugin.  In this situation, the only thing considered from the trunk `readme.txt`
    85 is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in
    86 your in-development version, without having that information incorrectly disclosed about the current stable version
    87 that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.
    88 
    89     If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
    90 you put the stable version, in order to eliminate any doubt.
    9171
    9272== Installation ==
    … …  
    130110
    131111== Changelog ==
     112= 1.0.2 =
     113* Edit screenshot and description for better compreshension
    132114
    133115= 1.0.1 =
    … …  
    144126
    145127== Upgrade Notice ==
     128= 1.0.2 =
     129* Update screenshot and description for better understanding
    146130
    147131= 1.0.1 =
Note: See TracChangeset for help on using the changeset viewer.