RECURRING_SALE

This page describes the Akurateco Android SDK RECURRING_SALE Adapter.

Overview

Recurring payments are commonly used to create new transactions based on already stored cardholder information from previous operations.

RECURRING_SALE request has same logic as SALE request, the only difference is that you need to provide primary transaction id, and this request will create a secondary transaction with previously used cardholder data from primary transaction.

RECURRING_SALE

1. The SALE Adapter operation method:

/**
 * @param termUrl3ds URL to which Customer should be returned after 3D-Secure. String up to 1024 characters.
 * @param auth indicates that transaction must be only authenticated, but not captured (AUTH or SALE).
 * @param callback the [AkuratecoSaleCallback].
 */
fun execute(
    @NonNull
    order: AkuratecoSaleOrder,
    @NonNull
    card: AkuratecoCard,
    @NonNull
    payer: AkuratecoPayer,
    @NonNull
    termUrl3ds: String,
    @Nullable
    options: AkuratecoSaleOptions? = null,
    @NonNull
    auth: Boolean,
    @NonNull
    callback: AkuratecoSaleCallback
)

If your account supports 3D-Secure, transaction result will be sent to your Notification URL.

2. The AkuratecoSaleCallback results:

• AkuratecoSaleResult.Success - success result.
• AkuratecoSaleResult.Decline - result with the decline reason.
• AkuratecoSaleResult.Recurring - result with the recurring parameters.
• AkuratecoSaleResult.Secure3D - result with the redirect parameters.

Go to SALE