Mints a barcode. BARCODE_LIMIT_EXCEEDED when Green Dot refuses for the
load limit or the barcode velocity limit.
Optionalamount?: numberFormat: double
OptionalamountMatchType?: 0 | 1 | 2Format: int32
0-No constraint, barcode can be consumed without constraint on amount. 1-Partial consumption, barcode must be consumed less than or equal to the amount specified in amount parameter(Not currently supported). 2-Full consumption, barcode must be consumed with exact amount specified in amount parameter. By default, amount_match_type is 0.
OptionalbarcodePaymentType?: 0 | 1 | 2 | 3Format: int32
OptionalbarcodeType?: 0 | 1 | 2 | 3 | 4Format: int32
OptionalipAddress?: stringOptionallatitude?: stringOptionallongitude?: stringOptionalnotificationChannelType?: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7Format: int32
OptionalpartnerTransactionReference?: stringOptionalrecipientAddress?: stringOptionalrecipientCustomerRef?: stringOptionalrecipientEmail?: stringOptionalrecipientFirstName?: stringOptionalrecipientLastName?: stringOptionalrecipientPhone?: stringOptionalrecipientZipcode?: stringFormat: int32
OptionalsenderAddress?: stringOptionalsenderCustomerRef?: stringOptionalsenderEmail?: stringOptionalsenderFirstName?: stringOptionalsenderLastName?: stringOptionalsenderPhone?: stringOptionalsenderZipcode?: stringReads one barcode. null when Green Dot answers BarcodeNotFound.
Any other error is a fault here: the caller named a barcode it minted.
The process client over the partner API, reading
greendot-partnerat each call.