AuthVoid

Cancels the transaction authorized in the Auth request (in case of 2-Phase). Return with appropriate response for the void result. On successful response, Green Dot will release the funds and the Partner is expected to release the Auth against the customer’s account. [Please see Appendix A for response code details.]

AnAuthVoid request can be sent in case a response was not received for the AuthRequest in a timely manner or a Void was sent by the Retailers POS within the Green Dot void delay timeframe.

Important Notes:

  • In the event a matching Auth Request was not found on the partner system, Green Dot expects an AuthVoidResponse with the ResponseCode “00”, indicating theAuth Request was notfound
  • In the event the partner already voided the transaction, Green Dot expects an AuthVoidResponse with the ResponseCode “00”, indicatingthe Auth was previously voided
  • The only instance an AuthVoidRequest should be rejected is when the partner finds the Auth request and explicitly declines the request to Void the transactionDiagrams below describe the structures of the AuthVoidRequestand AuthVoidResponseobjects:

Diagrams below describe the structures of the AuthVoidRequest and AuthVoidResponse objects:

Details of each attribute in the AuthVoidRequest and AuthVoidResponse objects are listed in the tables below:

AuthVoid Request

RequestHeader

FieldPartner-hosted/PUSH (Required?)GreenDothosted/PULL (Required?)TypeMax LengthDescription
CustomerANIOptionalOptionalString10Phone number area code first. To be provided if initiated by IVR. Must be all numerical digits Either CustomerIP or CustomerANI needs to be provided
CustomerIPOptionalOptionalString20Web users IP address. To be provided if initiated by Web.Either CustomerIP or CustomerANI needs to be provided
PartnerIPOptionalOptionalString20Partner’s IP address. To be provided if initiated by Web.
PartnerCodeYesYesString25Unique code to identify partner.
PasswordOptionalOptionalString512Password for authentication
UserNameOptionalOptionalString50UserName for authentication
ChannelYesYesIntegerN/A“1” for Unknown“2” for web application“3” for IVR“4” for Desktop“5” for Stores POS"6" for Mobile
RequestDateTimeYesYesDateTimeN/ATimestamp of Submitted Request in UTC time.
RequestIDYesYesString50Unique Request Identifier.
VersionYesYesString10Value = 2.0.0Format: ..
AmountYesOptionalDecimalN/ATransaction Amount.
DescriptionYesYesString255Description for this request
DictionaryEntryOptionalOptionalDictionary<string, string>N/AArray of key-value pairs.
OriginalRequestIDYesYesString50RequestID for the original TransactRequest or AuthCommitRequest
PaymentTypeYesYesIntegerN/A”0” for NULL
ProgramNumberYesYesString20Program identifier. Example: BIN, Settlement Group Reference ID

SourceAccount

Information regarding the Account from which the funds will be moved. Ex: MoneyPak

FieldPartner-hosted/PUSH (Required?)GreenDothosted/PULL (Required?)TypeMax LengthDescription
AccountNumberYesYesString50Account Number or Barcode number of the given AccountType.
AccountReferenceNumberOptionalOptionalString50Reference Number of the given AccountType.For Barcode funding, this will be the barcode transaction number. For MoneyPak, this is the PIN reference number. For Disbursements, this will be the Green Dot Customer reference number
AccountTypeYesYesIntegerN/A“1” for MoneyPak PIN
“4” for POS Cash Funding
“5” for Check Funding
“6” for Promotion Funding
“7” for Barcode Funding
“8” for Disbursement
“9” for Barcode Cash Pick-Up
SubAccountNumberN/AN/AString50
SubAccountReferenceNumberN/AN/AString50

TargetAccount

Information regarding the Account to which the funds will be moved. Ex: Partner’s Customer Account

FieldPartner-hosted/PUSH (Required?)GreenDothosted/PULL (Required?)TypeMax LengthDescription
AccountNumberYesYesString50Customer Account Number.
AccountReferenceNumberOptionalYesString50Partner's unique reference number identifying customer account.
AccountTypeYesYesIntegerN/A“2” for Partner’s Customer –Card
“3” for Partner’s Customer –Other
SubAccountNumberOptionalOptionalString50Customer’s sub account number.
SubAccountReferenceNumberOptionalOptionalString50Partner's unique reference number identifying customer’s sub-account.

AuthVoid Response

📘

FirstName, LastName, ZipCode are required for ALL GDN Partners, including Point of Banking (POB) Partners.

ResponseHeader

FieldPartner-hosted/PUSH (Required?)GreenDothosted/PULL (Required?)TypeMax LengthDescription
RequestIDYesYesString50Request Identifier echoed back from request
ResponseCodeYesYesString2Indicates successful and non-successful responses.
ResponseDateTimeYesYesDateTimeN/ATimestamp of response in UTC time.
ResponseIDYesYesString50Unique Response Identifier
ResponseTextYesYesString255Response code description.
VersionYesYesString10Value = 2.0.0Format: ..
DictionaryEntryOptionalOptionalDictionary<string, string>N/AArray of key-value pairs.

Sample Request/Response

Request

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><AuthVoid xmlns="http://greendotcorp.com/WebServices/Corporate/GDNPartnerAPI/"><request xmlns:a="https://partners.greendotcorp.com/GDCPartners/GDCWS_GDNPartnerAPI/" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><a:Auditi:nil="true"></a:Audit><a:Authentication><a:PartnerCode>GreenDot</a:PartnerCode><a:Password>*****</a:Password><a:UserName>*****</a:UserName></a:Authentication><a:Channel>5</a:Channel><a:RequestDateTime>2020-03-10T14:53:53.2066201Z</a:RequestDateTime><a:RequestID>AuthVoid2020-03-10T22:53:51</a:RequestID><a:Version>2.0.0</a:Version><a:Amount>500.0000</a:Amount><a:Description>AuthVoid by SoapUI</a:Description><a:DictionaryEntry xmlns:b="http://schemas.microsoft.com/2003/10/Serialization/Arrays"><b:KeyValueOfstringstring><b:Key>RetailerName</b:Key><b:Value>******</b:Value></b:KeyValueOfstringstring><b:KeyValueOfstringstring><b:Key>AuthCreateDate</b:Key><b:Value>2020-03-10 7:52:18 AM</b:Value></b:KeyValueOfstringstring></a:DictionaryEntry><a:OriginalRequestID>TestAuth2020-03-10T22:52:05</a:OriginalRequestID><a:PaymentType>0</a:PaymentType><a:ProgramNumber>********</a:ProgramNumber><a:SourceAccount><a:AccountNumber>PG*******************11</a:AccountNumber><a:AccountReferenceNumber>63********20</a:AccountReferenceNumber><a:AccountType>7</a:AccountType><a:SubAccountNumber i:nil="true"></a:SubAccountNumber><a:SubAccountReferenceNumber i:nil="true"></a:SubAccountReferenceNumber></a:SourceAccount><a:TargetAccount><a:AccountNumber>14************09</a:AccountNumber><a:AccountReferenceNumber>14************09</a:AccountReferenceNumber><a:AccountType>3</a:AccountType><a:SubAccountNumber i:nil="true"></a:SubAccountNumber><a:SubAccountReferenceNumber i:nil="true"></a:SubAccountReferenceNumber></a:TargetAccount></request></AuthVoid></s:Body></s:Envelope >

Response

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns3:AuthVoidResponse xmlns="https://partners.greendotcorp.com/GDCPartners/GDCWS_GDNPartnerAPI/" xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:ns3="http://greendotcorp.com/WebServices/Corporate/GDNPartnerAPI/" xmlns:ns4="http://schemas.microsoft.com/2003/10/Serialization/"><ns3:AuthVoidResult><RequestID>AuthVoid2020-03-10T22:53:51</RequestID><ResponseCode>00</ResponseCode><ResponseDateTime>2020-03-10T14:53:54.270Z</ResponseDateTime><ResponseID>6522173611763833359264732034138459</ResponseID><ResponseText>Success</ResponseText><Version>2.0.0</Version></ns3:AuthVoidResult></ns3:AuthVoidResponse></soap:Body></soap:Envelope >