Buckaroo
- Features
- UI Configuration/Processing Options Tab
- Supported Functionality
- Query Token Failure in Aria UI
- Mandate ID Transmission
- Webhook Notification Support Added for Buckaroo Smart Payments
- SEPA Direct Debit Refunds Added for Buckaroo Smart Payments
- Refunds for TCC Authorization Capture/Reversals for TCC Payments
- Recurring TCC Payments with an Authorization Token
- Transaction Logging
- iDEAL Direct Pay Method Supported via Aria APIs
- 3DS Authorization via APIs
Buckaroo is a leading payment service provider offering the most popular payment methods and in-store payment solutions to corporate organizations and subject matter experts in the e-commerce sector. As a payment partner, Buckaroo optimally serves companies in the further development of their payment strategy.
Features
- Tokenization
- Credit Card Processing (Authorization, Capture, Cancel, Reversal)
- Debit Card Processing (Authorization, Capture, Cancel, Reversal)
- Webhook/Event Notifications (Asynchronous Events and Chargeback)
- Soft Descriptor
UI Configuration/Processing Options Tab
The following fields are included at the Merchant Account Details tab:
| Field | Description |
|---|---|
| API URL | This is the Buckaroo endpoint URL used to make API calls. It is required at either the Payment Gateway or Collection Group level. The Collection Group value supersedes the Payment Gateway level value. |
| Website Key | This is the key provided by Buckaroo to identify a transaction with a specific merchant website. This key is also used for calculating HMAC SHA256 signature data. |
| Secret Key | This is the merchant secret key that is provided by the Buckaroo and it is used for generating the HMAC SHA256 hash as part of API authentication. |
The following fields are included at the Processing Options tab:
| Field | Description |
|---|---|
| 3DS Authentication Settings | |
| 3DS Notification URL |
This is the Return URL option for the authorization in which the customer will be redirected after completing 3DS authentication. You must specify the Merchant website URL (which will get invoked when the shopper challenge is complete). By default, it will be redirected to the URL which is configured by Buckaroo if no termination URL is configured. For Direct Post, this environment URL should match the Success Redirect URL in your Direct Post configuration (Configuration > Client Settings > U.S.S. Reg Configuration). |
Note: By default, all Tokenized Credit Cards go through the 3DS flow in Buckaroo. The following card types are suppored for 3DS:
- Visa
- Mastercard
- American Express
iDEAL Direct Pay Method Supported
Buckaroo supports iDEAL, an e-commerce payment system used for online banking in the Netherlands, as an alternative pay method. Prior to processing an iDEAL payment, one or more Return URL options must be configured (these determine where the customer will be redirected after completing an iDEAL payment).
To support this, Aria has introduced the following options to configure based on need (Configuration > Payments > [Payment Gateways/Collection Groups] > Processing Options tab):
| Label | Tooltip |
|---|---|
| Payment Return URL | The default URL where customers are redirected after payment. If left blank, the Payment Plaza URL is used. Configure other URLs for specific actions like cancel, error, or reject. |
| Payment Cancel Return URL | Alternative URL for transactions cancelled by the customer. |
| Payment Error Return URL | Alternative URL for transactions with processing errors. |
| Payment Reject Return URL | Alternative URL for rejected transactions. |
Additionally, Buckaroo supports iDEAL partial and full refunds, which can be issued through the Aria UI.
The following fields are included at the Field Options tab:
| Field | Description |
|---|---|
| soft_descriptor |
This is a transaction description shown on the buyer's credit card statement that displays a Merchant Name or Item Description. For additional charge identification, the invoice ID or sequential statement ID can be included by using the following tags: <Invoice_ID> For Tokenized Direct Debit SEPA (pay method 37 with IBAN for online/real-time payments), Aria now stores the soft descriptor value (configured either via API or UI). This will be used for sending at the time of batch payments. For example: ANWB-10001-19 (format for soft Descriptor: ANWB-<Invoice_ID> |
| end_user_ip_address | This is the IP address of the customer for whom the action is being performed. This value is used for fraud prevention. |
| end_user_browser_agent | This is the user agent of the client's web browser. This can be used for statistical purposes but also to perform anti-fraud checks on transactions. |
Aria supports the following SEPA payments through Braintree Smart Payments:
- Tokenized Credit Card (pay method 13)
- Direct Debit (pay method 26)
- Tokenized Direct Debit (pay method 37)
- iDEAL - Direct (pay method 49)
- ► Tokenized Credit Card Support
-
For Buckaroo Smart Payments, Aria now supports automatic Tokenized Credit Cards (pay method 13) for Visa, Mastercard, and American Express. The token is generated once after completing an initial payment.
The following actions are supported for Tokenized Credit Cards:
- Payment
- Authorization
- Authorize_3DS
- Capture
- Reversal
- Refund (full and partial)
- Query_Token
Notes:
- Buckaroo always expects 3DS authentication to be performed on all initial and subsequent transactions.
If passing a 3DS-enrolled card during a payment attempt, it will end up in payment failure ( = ERROR and = 791—Pending processing). In this situation, you must complete the 3DS process for your card using authorize_electronic_payment_m for tokenization. Once tokenized, you can use the card to make payments. Recurring payments are also supported ( = SUCCESS and = “190—Success”).
Supported Functionality
Query Token Failure in Aria UI
Error messaging has been enhanced for payment method creation failure to display the processor error response, as shown:
| Scenario | Status Code | Status Text |
|---|---|---|
| Unsupported Pay Method | UNSUPPORTED_PAY_METHOD | error.pay.method.not.supported.by.processor |
| Unsupported Action | UNSUPPORTED_ACTION | error.action.not.supported.by.processor |
| Unsupported CC ID | UNSUPPORTED_CC_ID | error.cc.id.not.supported.by.processor |
| Unsupported IBAN Indicator | UNSUPPORTED_IBAN_IND | error.iban.indicator.not.supported.by.processor |
| Unsupported business flow | UNSUPPORTED_RECURRING_AUTH | error.recurring.authorization.supported.by.processor |
Mandate ID Transmission
Aria also supports sending mandate details (mandate_id, mandate_signature_date) as part of a SEPA Direct Debit payment request (for a Buckaroo and external Mandate ID). If the mandate details are provided via APIs, we will honor the values and send the same to Buckaroo. If they are not provided, Aria will make use of mandate details generated by Buckaroo. This applies to both SEPA and Tokenized SEPA pay methods.
- ► Processing Mandate Details (Aria/Buckaroo)
-
mandate_id mandate_signature_date sequence Yes Yes Aria will store both the values send the same to Buckaroo—Existing behavior. Yes No Aria will honor the mandate_id provided in the API and send it to Buckaroo and update only mandate_signature_date returned by Buckaroo (i.e current date) notification. No Yes Aria will ignore the mandate_signature_date provided in the API request and use the mandate fields returned by Buckaroo notification. No No At the time of payment success in notification, Aria will update these two fields in the billing_info record sent by Buckaroo.
Webhook Notification Support Added for Buckaroo Smart Payments
As part of Buckaroo's Smart Payments integration, Aria introduces webhook notification support for Single Euro Payment Area (SEPA) payments (pay methods 26 for SEPA Direct Debit and 37 for SEPA Tokenized Direct Debit). This has been added for successful, failed, and reversed payments.
Note: As a reminder, webhooks are an automated means for applications to communicate with each other by sending data in real time; they are triggered by specific activity, such as invoicing of plan/account charges or data transmission initiated by system events within Aria client applications.
- ► Webhook Processing By Pay Method
-
Payment Method Webhook Event Behavior Direct Debit SEPA Payment (pay method=26) C004 For Success, Aria will update the proc_status_code as 1000, proc_status_text as message sent from Buckaroo and collection status as 3. Aria will also update the mandate_id and mandate_auth_date values. For Failure, Aria will update the proc_status_code as 2000, proc_status_text as message sent from Buckaroo and collection status as 5. Aria will also void the transaction. Tokenized Direct Debit SEPA Payment (pay method=37) C005 Same as above Direct Debit and Tokenized Direct Debit SEPA Reversal (pay methods 26 and 37) C501 Aria will update the proc_status_code as 2000, proc_status_text as message sent from Buckaroo and collection status as 5. Aria will also void the transaction.
SEPA Direct Debit Refunds Added for Buckaroo Smart Payments
Aria now supports Single Euro Payment Area (SEPA) Direct Debit and Tokenized Direct Debit (pay methods 26 and 37) for refunds via the Buckaroo Smart Payments integration. Buckaroo supports both full and partial refunds, which can be initiated and completed via the Aria UI and the issue_refund_to_acct_m API call.
This enhancement also includes transaction logging for the SEPA query_token pay action (pay method 37). Transaction logging is captured for both success and failure cases, handling different logging types (FULL, ERROR, SUMMARY, and NONE) when generating the transaction log entry.
Dunning support is also provided for payment failures as part of the webhook notification process. Additionally, if charges are applied to a child master plan instance (MPI), the child MPI (with parent pay) will be sent to Dunning in the event of payment failure.
Refunds for TCC Authorization Capture/Reversals for TCC Payments
The following TCC card brands support refunds for Authorization Capture/Reversals:
| Feature | VISA* | Mastercard* | American Express* |
|---|---|---|---|
| Authorization Capture (3DS and non-3DS authorization) | X | X | X |
| Authorization Reversal (3DS and non-3DS authorization) | X | X |
*-Tokenized Credit Card pay method
Recurring TCC Payments with an Authorization Token
Buckaroo does not support recurring or subsequent authorizations using a token. As per Buckaroo CC flow, Aria supports the tokenized credit card payment method. Once a token is generated for a given card during the initial authorization, Buckaroo only allows recurring payments, not recurring authorizations, using the created token. If a subsequent authorization with the token from the initial transaction is attempted, the transaction will fail.
Transaction Logging
Aria has also implemented transaction logging for iDEAL and SEPA/Tokenized SEPA payment types, as follows:
- Integrated transaction logging for iDEAL initial payment, query token, and refund (initial payment [pay method = 49] and recurring payment [pay method = 37]).
- Integrated transaction logging for SEPA (pay method = 26) refund.
- Integrated transaction logging for Tokenized SEPA (pay method = 37) query token and refund.
- Integrated transaction logging to capture logs in both success and failure scenarios.
- Integrated transaction logging to capture logs based on different logging types (FULL, SUMMARY, ERROR, NONE).
Transaction logging has also been implemented for Tokenized Credit Card payments (Visa, Mastercard and American Express), as follows:
- Integrated transaction logging for authorization, reversal, capture, payment, query_token, refund, and authorize_3ds actions.
- Integrated transaction logging to capture logs in both initial and recurring transactions.
- Integrated transaction logging to capture logs in both 3DS and non-3DS scenarios.
- Integrated transaction logging to capture logs in both success and failure scenarios.
- Integrated transaction logging to capture logs in all supported credit card types in Buckaroo.
- Integrated transaction logging to capture logs based on different logging types (FULL, SUMMARY, ERROR, and NONE).
iDEAL Direct Pay Method Supported via Aria APIs
Perform the following steps to enable iDEAL Direct payments:
- Once the invoice and statement is generated for the account, initiate the iDEAL payment using the record_alternative_payment_m API with the following inputs:
- <account_no>
- <reference_code>
- <payment_amount>
- <processor_id> (41 for Buckaroo)
- <pay_method_type> (49 for iDEAL—Direct pay method number)
- Once the record_alternative_payment_m API is executed with the above inputs, a <payment_redirect_issuer_url> is returned in the response.
- You should invoke this <payment_redirect_issuer_url> value in your browser to complete the iDEAL payment (where your customer is redirected to the issuer/bank page in which they will pass bank details and complete the payment).
- Once the iDEAL payment is completed, the status of the payment will be updated in Aria via webhook notification. As part of notification, Aria will also retrieve the token associated with the initial iDEAL payment and the new <billing_info> sequence for Tokenized Direct Debit will be created along with the token details.
- For subsequent transactions, you will use the new <billing_info> sequence (for the Tokenized Direct Debit pay method) created in the previous step.
Additionally, Buckaroo supports iDEAL partial and full refunds, which can be issued via the issue_refund_to_acct_m API.
3DS Authorization via APIs
For Buckaroo Smart Payments, 3DS authentication-based authorization has been added. As noted above, the 3DS Termination URL setting is the Return URL option for the authorization in which the customer will be redirected after completing 3DS authentication.
The 3DS authorization is a three-step process:
| Step Number | Description |
|---|---|
| 1 |
Execute the authorize_electronic_payment_m or update_payment_method_m api with pay_method=13 + credit card details to initiate the authorization, then the api will return the <proc_payment_id> (as the outer level output field) and <redirect_issuer_url> (value in the <proc_3dsecure_data/proc_3dsecure_auth_data> array) in the response. Note: If the supplied credit card is not-enrolled with the 3DS, then the 3DS flow will be skipped and regular authorization will be invoked here. In that event, the below steps would not be needed. |
| 2 | Use the <redirect_issuer_url> directly in the browser and execute it. A challenge/redirect window pops up based on the 3DS 2.0 or 3DS 1.0 transaction details; it would then be necessary to submit the challenge/redirect form to end step 2. |
| 3 | Execute authorize_3dsecure_m with the <proc_pymnt_id> (from step 1) and perform the authorization and verify the API result to complete the 3DS authentication-based authorization. |
The 3DS Termination URL setting (added as noted above) impacts the following APIs:
3DS Authorization is supported by the Visa, Mastercard and American Express card types.
The
assign_acct_plan_m authorize_electronic_payment_m create_acct_billing_group create_acct_complete_m update_acct_billing_group_m update_acct_complete_m update_acct_plan_multi_m update_payment_method_m
Also, to improve the clarity of error messages, the
For example:
“491 - Validation Failure” has been updated to “491 - Validation Failure; Parameter ‘CVV3’ is empty.”
“791 - Pending processing“ has been updated to “791 - Pending processing; C620 - Awaiting transfer to bank.”