Plugin Directory

Changeset 1393668


Ignore:
Timestamp:
04/13/2016 05:39:56 AM (10 years ago)
Author:
maratbn
Message:

Copied over the latest 'readme.txt' with the new screenshots info from the 'master--release--3.0' branch from the official repo, which is at: https://github.com/maratbn/RainbowPayPress

File:
1 edited

Legend:

Unmodified
Added
Removed
  • rainbowpaypress/tags/3.0.1/readme.txt

    r1392685 r1393668  
    127127Check if you have a mail transfer agent (MTA) installed and properly
    128128configured on your server.  Also check your SPAM folder.
     129
     130
     131== Screenshots ==
     132
     1331.  Examples of shortcode syntax, and display of all the transaction details entry fields that can
     134    be made available to the buyer on any page of the website.
     135
     1362.  The official Stripe Checkout Dialog that appears when the buyer clicks to enter the Stripe
     137    token id or Stripe card email fields.
     138
     1393.  RainbowPayPress admin menu.
     140
     1414.  Example of transaction details entry fields filled out by the buyer just before transaction
     142    submission.
     143
     1445.  Transaction submission confirmation message displayed to the buyer after transaction
     145    submission.  The confirmation message includes the timestamp of the submission and the Stripe
     146    token that can be used by the website administrator(s) to charge the buyer's credit card.
     147
     1486.  The 'Pending Transactions' and 'Charged Transactions' tables as they appear to the website
     149    administrator(s) on the 'Transactions' admin page, containing the data for example
     150    transactions.  New transactions are initially inserted as new rows to the top of the 'Pending'
     151    table,  Clicking the 'Charge' button charges the transaction, and moves the associated record
     152    to the top of the 'Charged' table.  The 'Charged' table contains additional columns 'Customer
     153    ID' and 'Charge ID'.  These data tokens are created by the Stripe business logic when the
     154    transaction is charged, and they are rendered as web links, clicking on which takes the user to
     155    the associated records on their Stripe account on the Stripe website.
     156
     1577.  The 'Items' table as it appears to the website administrator(s), containing an example list of
     158    items that can be specified for sale via RainbowPayPress shortcodes.
     159
     1608.  The RainbowPayPress 'Settings' page as it appears to the website administrator(s) with some
     161    example settings.
     162
     1639.  A screenshot of a customer record as it appears on the Stripe website.  This record was created
     164    when the associated transaction was charged by clicking on the 'Charge' button on its row on
     165    the 'Pending Transaction' table on the 'Transactions' admin page.  Once a transaction is
     166    charged, all records associated with that charge can be tracked on the user's Stripe account.
    129167
    130168
Note: See TracChangeset for help on using the changeset viewer.