package payments

Get desktop application:
View/edit binary Protocol Buffers messages

Generalized form of "send payment to this/these raven addresses"

Used in: Payment, PaymentDetails

• optional uint64 amount = 1

  amount is integer-number-of-satoshis

• required bytes script = 2

  usually one of the standard Script forms

Used in: PaymentACK

• optional bytes merchant_data = 1

  From PaymentDetails.merchant_data

• repeated bytes transactions = 2

  Signed transactions that satisfy PaymentDetails.outputs

• repeated Output refund_to = 3

  Where to send refunds, if a refund is necessary

• optional string memo = 4

  Human-readable message for the merchant

• required Payment payment = 1

  Payment message that triggered this ACK

• optional string memo = 2

  human-readable message for customer

• optional string network = 1

  "main" or "test"

• repeated Output outputs = 2

  Where payment should be sent

• required uint64 time = 3

  Timestamp; when payment request created

• optional uint64 expires = 4

  Timestamp; when this request should be considered invalid

• optional string memo = 5

  Human-readable description of request for the customer

• optional string payment_url = 6

  URL to send Payment and get PaymentACK

• optional bytes merchant_data = 7

  Arbitrary data to include in the Payment message

• optional uint32 payment_details_version = 1

• optional string pki_type = 2

  none / x509+sha256 / x509+sha1

• optional bytes pki_data = 3

  depends on pki_type

• required bytes serialized_payment_details = 4

  PaymentDetails

• optional bytes signature = 5

  pki-dependent signature

• repeated bytes certificate = 1

  DER-encoded X.509 certificate chain