Broker Overview - Revision history

Cocodude at 10:27, 24 November 2015

2015-11-24T10:27:45Z

← Older revision		Revision as of 10:27, 24 November 2015
Line 1:		Line 1:
	Once you are authorised as a ~~seller~~, you should have access to the ''Seller'' button in the navigation panel.		Once you are authorised as a broker, you should have access to the ''Seller'' button in the navigation panel.

	===Terminology===		===Terminology===

	Each ~~seller~~ has one or more ''offers'' available, which is a combination of the following:		Each broker has one or more ''offers'' available, which is a combination of the following:
	* Country		* Country
	* Currency		* Currency
Line 11:		Line 11:
	For instance, you might have an offer available called ''GBP→BTC / GB / BANK'' which means that it is available for people buying BTC in Great British Pounds in Great Britain (which for purposes here includes Northern Ireland, Isle of Man, Jersey and Guernsey) via UK bank transfer.		For instance, you might have an offer available called ''GBP→BTC / GB / BANK'' which means that it is available for people buying BTC in Great British Pounds in Great Britain (which for purposes here includes Northern Ireland, Isle of Man, Jersey and Guernsey) via UK bank transfer.

	===How a ~~seller~~ gets chosen===		===How a broker gets chosen===

	If you are the ~~seller~~ that fits the following criteria, the ~~buyer~~ will be given your payment details and the trade will be yours to complete:		If you are the broker that fits the following criteria, the user will be given your payment details and the trade will be yours to complete:

	* The country matches your offer country.		* The country matches your offer country.
	* The currency matches your offer currency.		* The currency matches your offer currency.
	* You have this amount of Bitcoins available (taking away any coins in escrow).		* You have this amount of Bitcoins available (taking away any coins in escrow).
	* You are offering coins at a price ~~cheaper~~ than anyone else.		* You are offering coins at a more competitive price than anyone else.

	Note that if two or more sellers are offering coins at an equally ~~cheap~~ price, Bittylicious chooses one of these ~~sellers~~ at random.		Note that if two or more sellers are offering coins at an equally competitive price, Bittylicious chooses one of these brokers at random.

	===~~Trade~~ timeline===		===User purchase timeline===

	# The ~~buyer~~ initiates a trade. The trade starts in the ''ACCEPTED'' state.		# The user initiates a trade. The trade starts in the ''ACCEPTED'' state.
	# The ~~buyer~~ sees your payment details.		# The user sees your payment details.
	# The ~~buyer~~ makes payment using online banking.		# The user makes payment using online banking.
	# The ~~buyer~~ clicks ''I have sent payment''. The trade progresses to the ''PAID'' state.		# The user clicks ''I have sent payment''. The trade progresses to the ''PAID'' state.
	# If the ~~seller~~ has ''Send email on payment?'' set to ''Yes'' in your profile, he/she will be sent an email saying that payment has been completed.		# If the broker has ''Send email on payment?'' set to ''Yes'' in your profile, he/she will be sent an email saying that payment has been completed.
	# If the ~~seller~~ is trading automatically:		# If the broker is trading automatically:
	## The ~~seller~~'s bank software logs into the bank account at regular intervals.		## The broker's bank software logs into the bank account at regular intervals.
	## If a matching transaction (price and reference) is found, the software notifies Bittylicious.		## If a matching transaction (price and reference) is found, the software notifies Bittylicious.
	# If the ~~seller~~ is trading manually:		# If the broker is trading manually:
	## The ~~seller~~ checks his/her bank account at regular periods within the two hour window.		## The broker checks his/her bank account at regular periods within the two hour window.
	## The ~~seller~~ sees a payment that matches the amount and reference and does not look suspicious.		## The broker sees a payment that matches the amount and reference and does not look suspicious.
	## The ~~seller~~ goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.		## The broker goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.
	## The ~~seller~~ copies and pastes the output into the text box. This will always end in a ''=''. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.		## The broker copies and pastes the output into the text box. This will always end in a ''=''. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.
	## The ~~seller~~ enters the bank account name the payment appeared to come from (see the section below).		## The broker enters the bank account name the payment appeared to come from (see the section below).
	## The ~~seller~~ clicks ''Force complete''.		## The broker clicks ''Force complete''.
	# The trade changes to a ''COMPLETING'' stage.		# The trade changes to a ''COMPLETING'' stage.
	# After 3-30 seconds, the trade changes to a ''RECEIVED'' state, or an ''ERROR'' state if an error occurred.		# After 3-30 seconds, the trade changes to a ''RECEIVED'' state, or an ''ERROR'' state if an error occurred.

Cocodude: Cocodude moved page Seller Overview to Broker Overview

2015-11-24T10:24:46Z

Cocodude moved page Seller Overview to Broker Overview

← Older revision	Revision as of 10:24, 24 November 2015
(No difference)

Cocodude at 15:58, 27 October 2014

2014-10-27T15:58:31Z

← Older revision		Revision as of 15:58, 27 October 2014
Line 41:		Line 41:
	# The trade changes to a ''COMPLETING'' stage.		# The trade changes to a ''COMPLETING'' stage.
	# After 3-30 seconds, the trade changes to a ''RECEIVED'' state, or an ''ERROR'' state if an error occurred.		# After 3-30 seconds, the trade changes to a ''RECEIVED'' state, or an ''ERROR'' state if an error occurred.

			===Account name this came from===

			The details that should be filled in this box vary by payment method. In all cases though, it should be identifying information identifying the sender's account. For most payment methods, thus should be an account name the payment came from, with the following exceptions:

			* Natwest/RBS PYC: Sender's phone number

	===Why do I need to sign trades?===		===Why do I need to sign trades?===

Cocodude: /* Trade timeline */

2014-10-27T15:56:42Z

Trade timeline

← Older revision		Revision as of 15:56, 27 October 2014
Line 37:		Line 37:
	## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.		## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.
	## The seller copies and pastes the output into the text box. This will always end in a ''=''. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.		## The seller copies and pastes the output into the text box. This will always end in a ''=''. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.
	## The seller enters the bank account name the payment appeared to come from.		## The seller enters the bank account name the payment appeared to come from (see the section below).
	## The seller clicks ''Force complete''.		## The seller clicks ''Force complete''.
	# The trade changes to a ''COMPLETING'' stage.		# The trade changes to a ''COMPLETING'' stage.

Cocodude: /* Terminology */

2014-04-22T19:42:45Z

Terminology

← Older revision		Revision as of 19:42, 22 April 2014
Line 3:		Line 3:
	===Terminology===		===Terminology===

	Each seller has one or more ''offers'' available, which is a combination of ~~countries and~~ currency. For instance, you might have an offer available called ''~~GBP~~ / GB'' which means that it is available for people ~~paying~~ in Great British Pounds in Great Britain (which for purposes here includes Northern Ireland, Isle of Man, Jersey and Guernsey).		Each seller has one or more ''offers'' available, which is a combination of the following:
			* Country
			* Currency
			* Virtual currency (e.g. BTC)
			* Payment method
			* Direction (selling or buying)
			For instance, you might have an offer available called ''GBP→BTC / GB / BANK'' which means that it is available for people buying BTC in Great British Pounds in Great Britain (which for purposes here includes Northern Ireland, Isle of Man, Jersey and Guernsey) via UK bank transfer.

	===How a seller gets chosen===		===How a seller gets chosen===

Cocodude: /* Terminology */

2014-04-03T22:14:33Z

Terminology

← Older revision		Revision as of 22:14, 3 April 2014
Line 3:		Line 3:
	===Terminology===		===Terminology===

	Each seller has one or more ''offers'' available, which is a combination of countries and currency. For instance, you might have an offer available called ''GBP / GB'' which means that it is available for people paying in Great British Pounds in Great Britain (which for purposes here includes ~~North~~ Ireland, Isle of Man, Jersey and Guernsey).		Each seller has one or more ''offers'' available, which is a combination of countries and currency. For instance, you might have an offer available called ''GBP / GB'' which means that it is available for people paying in Great British Pounds in Great Britain (which for purposes here includes Northern Ireland, Isle of Man, Jersey and Guernsey).

	===How a seller gets chosen===		===How a seller gets chosen===

Cocodude: /* Trade timeline */

2014-02-28T10:18:34Z

Trade timeline

← Older revision		Revision as of 10:18, 28 February 2014
Line 30:		Line 30:
	## The seller sees a payment that matches the amount and reference and does not look suspicious.		## The seller sees a payment that matches the amount and reference and does not look suspicious.
	## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.		## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.
	## The seller copies and pastes the output into the text box. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.		## The seller copies and pastes the output into the text box. This will always end in a ''=''. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.
	## The seller enters the bank account name the payment appeared to come from.		## The seller enters the bank account name the payment appeared to come from.
	## The seller clicks ''Force complete''.		## The seller clicks ''Force complete''.

Cocodude: /* Trade timeline */

2014-01-17T23:49:56Z

Trade timeline

← Older revision		Revision as of 23:49, 17 January 2014
Line 30:		Line 30:
	## The seller sees a payment that matches the amount and reference and does not look suspicious.		## The seller sees a payment that matches the amount and reference and does not look suspicious.
	## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.		## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.
	## The seller copies and pastes the output into the text box.		## The seller copies and pastes the output into the text box. If you are copy and pasting from Windows, ensure that you are not pasting additional new line or space characters.
	## The seller enters the bank account name the payment appeared to come from.		## The seller enters the bank account name the payment appeared to come from.
	## The seller clicks ''Force complete''.		## The seller clicks ''Force complete''.

Cocodude: /* Trade timeline */

2014-01-06T21:25:25Z

Trade timeline

← Older revision		Revision as of 21:25, 6 January 2014
Line 29:		Line 29:
	## The seller checks his/her bank account at regular periods within the two hour window.		## The seller checks his/her bank account at regular periods within the two hour window.
	## The seller sees a payment that matches the amount and reference and does not look suspicious.		## The seller sees a payment that matches the amount and reference and does not look suspicious.
	## The seller goes to the seller trade page and runs the PHP command just ~~left of~~ the ''~~Complete trade~~'' box.		## The seller goes to the seller trade page and runs the PHP command just under the ''Account name this came from'' box. This command begins ''php sign.php''. Do not, under any circumstances, paste your private key in here.
	## The seller copies and pastes the output into the text box.		## The seller copies and pastes the output into the text box.
	## The seller enters the bank account name the payment appeared to come from.		## The seller enters the bank account name the payment appeared to come from.

Cocodude: /* Trade timeline */

2013-10-16T14:31:23Z

Trade timeline

← Older revision		Revision as of 14:31, 16 October 2013
Line 31:		Line 31:
	## The seller goes to the seller trade page and runs the PHP command just left of the ''Complete trade'' box.		## The seller goes to the seller trade page and runs the PHP command just left of the ''Complete trade'' box.
	## The seller copies and pastes the output into the text box.		## The seller copies and pastes the output into the text box.
	## The seller enters the bank account name the payment appeared to come from ~~(if applicable)~~.		## The seller enters the bank account name the payment appeared to come from.
	## The seller clicks ''Force complete''.		## The seller clicks ''Force complete''.
	# The trade changes to a ''COMPLETING'' stage.		# The trade changes to a ''COMPLETING'' stage.