complete_paypal_token_creation_m Guide
- Last updated
-
-
Save as PDF
-
The complete_paypal_token_creation_m API confirms that a billing agreement has been accepted by the account user, and that PayPal is able to authorize a payment against that billing agreement. The token is a PayPal session token created by the init_paypal_token_creation_m call. If the billing agreement was accepted, then Aria saves the associated agreement identifier in the database to use for future transactions with this account.The merchant must have their PayPal Payment Receiving Preferences (under Profile on PayPal) set to block "pay with eCheck" (the box must be checked, and this does not prevent PayPal users from funding transactions with their bank account). If this is not done, any end user who needs to pay remaining balances (beyond the amount in their PayPal account) with a bank account will be unable to make payments. When the box is checked, such bank account funded payments will be secured by the user's credit card in case the bank account transfer fails. The merchant may also choose to have alternate currencies converted to their primary currency on that screen. Merchants who would like to collect in multiple currencies should either elect to convert there, or add additional Currency Balances in their PayPal Profile. If Billing group inputs are provided, then we will try to attempt the token creation action using the Billing group's Collection group and store the created payment method as the primary pay method of the billing group. Please note these Billing group inputs are optional. If Billing group inputs are not provided, then we will use the account's Collection group. We need to ensure consistency when providing billing group inputs for the init_paypal_token_creation_m and complete_paypal_token_creation_m APIs. If billing group inputs are provided, they must be included in both APIs. Otherwise, they can be skipped from both APIs.
Additional Guidance
Output Fields
| Field |
Description |
| <do_auth_reversal> |
Determines whether to reverse the authorization immediately. If setting is 0 and a reversal is desired later, it would require using the reverse_authorized_electronic_payment_m API
| Values |
Description |
| -1 |
Use Configuration Settings |
| 0 |
Will not reverse the authorization |
| 1 |
Will reverse the authorization |
|
| <update_avs_return_address> |
Specifies how to handle an AVS return address - send an address verification request. This value will override any client-level configuration setting in the Payment Gateways or Collection Groups section of the UI. Description
| Values |
Description |
| -1 |
Use Configuration Settings (default) |
| 0 |
Do not update Aria billing address from PPEC AVS results and ignore results. |
| 1 |
Update Aria billing address from PPEC AVS results. |
|
| <disable_pmt_on_auth_failure> |
Determines to update the payment failure while completing the token creation and disable the payment method. Default is 0 - we don't update the payment auth record and allow the client to retry complete the token creation. If client provides 1, then we will update the payment failure in the payment auth record and disable the payment method.
| Values |
Description |
| 0 |
Do not update the payment_auth record and payment method remains active (default). |
| 1 |
Update the payment_auth record with failure status and disable the payment method. |
|