At times, it is helpful to add additional language to various payment pages in places where language does not exist.
Previously,the only alternative was to edit the template files directly - but these files are prone to overwrite when installing patches.
The RCI system offers some interesting possibilities there, provided you are careful not to prematurely output to the web.
Here are two example files which, when placed in your catalog/includes/runtime/checkout_payment directory (create this if it does not exist).
AUTHNET_checkout_payment_insideformabovebuttons.php
<?php
$rci = '<tr><td>'. "\n";
$rci .= '<h1>Press Continue to Confirm Your Order</h1>'. "\n";
$rci .= '<p>You can shop online at www.OurSplendidSite.com with confidence. All payments are processed via PCI compliant secure connections. For your protection, we verify your cards <b>Billing address</b>. You must have JavaScript enabled to use this site.</p>'. "\n";
$rci .= '</td></tr>' . "\n";
return $rci;
?>
AUTHNET_checkout_payment_insideformbelowbuttons.php
<?php
$rci = '<tr><td>'. "\n";
$rci .= '<h1>In the event you experience difficulty processing your card,</h1>'. "\n";
$rci .= '<h1>Please contact us Toll Free: (8**) ***-****</h1>'. "\n";
$rci .= '<h1>We will be happy to assist you in processing your order.</h1>'. "\n";
$rci .= '</td></tr>' . "\n";
return $rci;
?>
Note that the code does not echo or print to the screen, it simply builds a string and returns it. Also important is the form of the HTML - which in each of these cases must be a complete table row or rows.