Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tree: 166a084ab6
Fetching contributors…

Cannot retrieve contributors at this time

34 lines (24 sloc) 2.629 kB
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Ripple Union Credit Reports</title>
<link rel="stylesheet" type="text/css" href="/assets/common.css" />
</head>
<body>
<h1><img src="/assets/logo.png" alt="Ripple Union" /> Credit Reports</h1>
{{#forForm}}
<form method="get" action="{{formAction}}">
<input type="text" name="address" placeholder="Ripple.com address" />
<input type="submit" value="View Report" />
</form>
{{/forForm}}
<p>This credit reporting system is designed to give support to Ripple.com organizations and users who want to extend credit to other users. Every time a user to whom you have extended credit makes a payment on that credit, you may submit an OpenPGP signed message saying:</p>
<blockquote>&lt;unix timestamp of transaction&gt;: &lt;Ripple.com address of user&gt; made a payment</blockquote>
<p>If you have an agreement that payments should be made, and a user does not uphold this agreement, the format is the same as above but you say "missed a payment". If the user makes a payment, but then executes a chargeback (if you have, say, agreed to PayPal payments), you say "chargeback". If a user consistently behaves in an untrustworthy manner, say "not trusted". There are links on individual report pages to messages of the various types that you can simply download, sign with your OpenPGP key, and then upload again using the submit form for that address.</p>
<p>Note: <strong>signing subkeys are not supported</strong>. This is a technical limitation we hope will be lifted soon.</p>
<p>Submitted assertions <em>must</em> be valid, non-expiring OpenPGP signatures made by a valid key. We get keys from the public keyservers. If your key is not on the public keyservers, you can <a href="http://singpolyma.net:11371/">submit it</a>.</p>
<p><strong>Do not blindly trust assertions</strong>. Verify the identity of the key that made the assertion. Do you trust this person or organization? If you don't know who it is, ask around in the community. If you want to tie your OpenPGP key to your community identity, you might consider <a href="https://ripple.com/forum/viewtopic.php?f=1&amp;t=1617">this forum thread</a>.</p>
<p>Do you accept payments through an automated system? Want an API? No problem. Request JSON or JSONP from a report page to get a machine-readable report. Put a signed assertion in the body of a POST to any report URI to add an assertion to that URI, errors can be returned as text or JSON.</p>
</body>
</html>
Jump to Line
Something went wrong with that request. Please try again.