Integration

Supported actions, payment flow and requirements for Zakelijk op Rekening

Zakelijk op Rekening uses the In3 service with the Route parameter set to AbnB2b. The service supports three actions:

  • Authorize
  • Capture
  • Refund

Route is mandatory

Every request must contain the Route parameter with the value AbnB2b.
Without this parameter the transaction is handled as a regular In3 transaction, which does not support the Authorize and Capture actions.


Payment flow

1. Authorize

You send an Authorize request with the order data, the article lines and the company details of the buyer. Buckaroo forwards the request to ABN AMRO, which performs the credit and fraud check.

If the check is approved, the response contains a redirect URL. Redirect the customer to this URL to complete the order.

The authorization reserves the amount. No invoice is created and no money is collected at this point.

2. Capture

Capture the transaction once the order is shipped or the service is delivered. Reference the original authorization through the OriginalTransactionKey.

The capture is the moment the invoice is created and sent to the buyer by ABN AMRO. Capture therefore has to match what the buyer actually receives.

The capture amount may be equal to or lower than the authorized amount:

  • If the capture amount equals the authorized amount, the article lines from the Authorize request are reused and invoice lines are optional.
  • If the capture amount is lower, invoice lines are mandatory. Send the lines that are actually being shipped.

3. Refund

Use Refund to refund a captured transaction, in full or in part. Reference the captured transaction through the OriginalTransactionKey.


Requirements

RequirementDetails
AmountOrder value from EUR 250 to EUR 25,000
CurrencyEUR
BuyerA registered business, verified by ABN AMRO. Consumer orders are not supported
Customer categoryCategory of the billing customer must be B2B
Company detailsCompany name and Chamber of Commerce number of the buyer
Billing countryThe Netherlands
Seller countryThe Netherlands

An order outside the amount range is rejected.

Returns and cancellations

Report a cancellation or a return so the invoice of the buyer is adjusted. A full return releases the buyer from the invoice, a partial return leads to a credit note. Handle this through a Refund on the captured transaction, and make sure the amount matches the goods actually returned.


Push messages

Buckaroo sends a push message for the authorization, the capture and the refund. Handle the status in your push handler rather than on the return URL, because the return URL may not always be reached.

The relevant status codes are the standard Buckaroo codes. See Status for the full overview.

CodeMeaningAction
190SuccessThe authorization or capture succeeded
490FailedThe credit check was rejected or the transaction failed
690RejectedThe transaction was rejected
790Pending inputWaiting for customer input
791Pending processingWaiting for the customer to complete the redirect
890Cancelled by userThe customer cancelled the transaction

Transaction types

Transaction typeAction
I027Authorize
C063Capture
C203Refund

Order management

Because the invoice is created at capture, the capture moment determines when the payment term of the buyer starts. Align your order workflow accordingly:

  • Capture on shipment for physical goods.
  • Capture on delivery or activation for services.
  • Capture partially when you ship partially, and send the matching invoice lines.

An authorization that is never captured expires. Contact Buckaroo support for the expiry term that applies to your account.

Testing

Test transactions run through the Buckaroo test environment in the same way as regular In3 transactions. See Testing for the general instructions and request the test company details from Buckaroo support, because the credit check is performed against test data supplied by ABN AMRO.


Did this page help you?