Straight Send
Straight Send is an innovative payment system for fast and convenient fund transfers to eligible debit cards. This Straight Send payment method credits funds to a recipient’s Debit Card account. Straight Send payment method tends to be cheaper, faster, more convenient and more traceable than traditional payment methods.
In this section:
For the entire list of API endpoints, refer to API Endpoints.
Request
Field name | Description | Required | Length | Data type |
---|---|---|---|---|
ssl_merchant_id | Merchant ID Elavon-assigned Converge Account ID (AID). | Required | 6 or 7 | numeric |
ssl_user_id | Converge User ID The user ID with Hosted Payment API User status that can send transaction requests through the terminal. | Required | 15 | alphanumeric |
ssl_pin | Terminal ID Unique identifier of the terminal that will process the transaction request and submit to the Converge gateway. error_outline important The | Required | 64 | alphanumeric |
ssl_amount | Transaction Amount The Sale amount that includes the Net and Sales Tax amount Format: Number with 2 decimal places | Required | 11 | Numeric |
ssl_transaction_type | Transaction Type Valid value: dboctdisbursement | Required | 20 | alphanumeric |
ssl_card_number | Card Number Unique card identification number. Card length: 18 - Debit Card | Required | 18 or 19 | numeric |
ssl_exp_date | Card’s Expiry Date Date when the card becomes invalid. Format: MMYY | Required | 4 | numeric |
ssl_oct_ref_number | OCT Reference Number This field is used to identify the sender reference number submitted with the Original Credit Transaction (OCT) | Required | 16 | numeric |
Response
Field name | Description |
---|---|
ssl_amount | Total Authorized/Approved Transaction Amount Return based on merchant setup |
ssl_approval_code | Transaction Approval Code Unique code returned by the credit card processor that indicates the approval status of the transaction. |
ssl_card_number | Masked Card Number Converge only returns the first 2 or last 4 digits of the regular PAN |
ssl_card_type | Payment Type Valid value: DEBITCARD |
ssl_card_short_description | Short Card Brand Name Valid values are: MC and VISA . |
ssl_exp_date | Card’s Expiry Date Returned based on merchant setup Format: MMYY |
ssl_transaction_currency | Transaction Currency |
ssl_txn_id | Transaction ID Unique identifier of the transaction. |
ssl_txn_time | Processing Date and Time Indicates when Converge processed the transaction. Format: MM/DD/YYYY hh:mm:ss AM/PM Example: 03/18/2010 10:34:10 AM |
ssl_transaction_type | Transaction Type |
ssl_issuer_response | Original Issuer Response The issuer response returned during the authorization attempt. An ssl_issuer_response = 00 indicates success.An ssl_issuer_response not equal to 00 indicates a decline or failure. |
ssl_result | Transaction Outcome An ssl_result = 0 indicates an approved transaction.An ssl_result not equal to 0 indicates a declined and unauthorized transaction. |
ssl_result_message | Transaction Result Message Refer to the Debit Card Response Codes section for an extensive list of possible returned messages. |
[Card On File] | |
ssl_oar_data | Original Authorization Response Data This data will be as received during the original authorization processing. This is a retain and return value for terminal-based settlement messages. You may store this field with the payment details from the transaction to make future Card On File transactions. |
ssl_ps2000_data | PS2000 This data will be as received during the original authorization processing. This is a retain and return value for terminal-based settlement messages. You must store this field with the payment details from the transaction to make future Card On File transactions. |
Examples
Request
xmldata=
<txn>
<ssl_merchant_id>Merchant Account ID</ssl_merchant_id>
<ssl_user_id>API User ID</ssl_user_id>
<ssl_pin>Unique Terminal Identifier</ssl_pin>
<ssl_amount>1.00</ssl_amount>
<ssl_transaction_type>dboctdisbursement</ssl_transaction_type>
<ssl_card_number>4000XXXXXXXX0001</ssl_card_number>
<ssl_exp_date>MMYY</ssl_exp_date>
<ssl_oct_ref_number>1234567890123456</ssl_oct_ref_number>
</txn>
Response
<txn>
<ssl_result>0</ssl_result>
<ssl_issuer_response>00</ssl_issuer_response>
<ssl_result_message>APPROVAL</ssl_result_message>
<ssl_card_number>50**********3003</ssl_card_number>
<ssl_oar_data>9898 9889999999 9</ssl_oar_data>
<ssl_txn_id>110620AD2-880072A9-628C-4556-9EAF-B2C54C0F1BBB</ssl_txn_id>
<ssl_approval_code>N01032</ssl_approval_code>
<ssl_amount>1.00</ssl_amount>
<ssl_transaction_currency>USD</ssl_transaction_currency>
<ssl_txn_time>06/11/2020 12:01:35 PM</ssl_txn_time>
<ssl_exp_date>1220</ssl_exp_date>
<ssl_card_short_description>VI</ssl_card_short_description>
<ssl_card_type>DEBITCARD</ssl_card_type>
<ssl_transaction_type>OCTDISBURSEMENT</ssl_transaction_type>
<ssl_ps2000_data>X878787</ssl_ps2000_data>
</txn>