RECURRING_SALE - edfapay/edfa-pg-android-sdk GitHub Wiki
This page describes the EdfaPg 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
- The RECURRING_SALE Adapter operation method based on the cardholder data:
/**
* @param payerEmail customer’s email. String up to 256 characters.
* @param cardNumber the credit card number.
* @param auth indicates that transaction must be only authenticated, but not captured.
* @param callback the [EdfaPgSaleCallback].
*/
fun execute(
@NonNull
order: EdfaPgOrder,
@NonNull
options: EdfaPgRecurringOptions,
@NonNull
payerEmail: String,
@NonNull
cardNumber: String,
@NonNull
auth: Boolean,
@NonNull
callback: EdfaPgSaleCallback
)
- The RECURRING_SALE Adapter operation method based on the hash data:
/**
* @param hash special signature to validate your request to payment platform.
* @param auth indicates that transaction must be only authenticated, but not captured.
* @param callback the [EdfaPgSaleCallback].
*/
fun execute(
@NonNull
order: EdfaPgOrder,
@NonNull
options: EdfaPgRecurringOptions,
@NonNull
hash: String,
@NonNull
auth: Boolean,
@NonNull
callback: EdfaPgSaleCallback
)
Response from Payment Platform is the same as by SALE command, except for the value of the difference parameter "action=RECURRING_SALE".
- The
EdfaPgSaleCallback
results:
Result | Description |
---|---|
EdfaPgSaleResult.Success |
success result. |
EdfaPgSaleResult.Decline |
result with the decline reason. |
EdfaPgSaleResult.Recurring |
result with the recurring parameters. |
EdfaPgSaleResult.Secure3D |
result with the redirect parameters. |