There are three ways to initiate a refund:
- A merchant-initiated refund using the AT&T API Platform Payment API
- A customer-initiated refund through the Online Assistance Center
- An AT&T Customer Service Representative-initiated refund through the Customer Care Center
Merchant-initiated refunds cancel the subscription immediately and stop the most recent payment. Customer Service Representatives have these options:
- Cancel the subscription immediately and refund the full amount
- Put the subscription in the "Do Not Renew" state which prevents the next payment transaction from happening.
The monthly detailed transaction reports contain records of the original transaction, as well as the refunds. The refund records contain the transaction ID of the original transaction, so that the purchase and refund can be easily correlated.
The Payment API is designed to protect the consumer's identifying information. Transactions and subscriptions have a ConsumerId value, but that value is a random key that may not be persistent.
It is the account number used in all back-end financial accounting systems.
This is required when creating a new subscription and must be a unique string. The XML status response for a subscription will contain this value with the name, merchantSubscriptionId. It is required for the Subscription Details request. We recommend that you use the same value as the MerchantTransactionId.
These settings are used to differentiate between Payment Notifications related to "production" apps versus Payment Notifications related to sandbox apps, for a given AT&T Merchant account.
Sales conversion rates are driven by a number of factors, such as the product itself, the quality, the promotion, and the friction encountered in the purchase process. Payment API can provide a simple, low-friction payment process that can make it easy for your prospective customer to be converted in to a sale.
The developer or content owner is primarily responsible for addressing subscriber issues associated with the application or content being sold. AT&T Customer Care is the final serving contact and escalation point.
The Payment API can support sales of digital and virtual goods and in-app billing, including one-time and subscription purchases, via any internet-connected device.
Settlement is supported with a simple invoice presentation that includes enough details for developers to understand the sales and costs of apps. Appropriate contact information is provided in case customers have disputes or questions. The system also provides revenue assurance, which includes details on collections, refunds, suspensions, and terminations.
At this time, the New Transaction and Get Transaction Status methods are the only Payment API methods available for developers to implement in their applications.
Contact the AT&T Developer Support Program for details about Payment API methods.
The Payment API provides the functionality to handle the authentication, capture use consent, confirmation, and invoice posting process for a purchase, so that you don't have to develop these functionalities yourself. Payment API gives you the control and flexibility to manipulate the look and feel of how you present your customers with purchase options, as well as how you deliver digital goods to your customers.
IsPurchaseOnNoActiveSubscriptionmust be set to "false"
- Category 2, Virtual Goods, is not allowed for Subscriptions
SubscriptionRecurringNumbermust be set to "99999"
MerchantTransactionIdmust be unique
MerchantSubscriptionIdListmust be a single value, and that must be unique
SubscriptionRecurringPeriodmust be "MONTHLY"
SubscriptionRecurringPeriodAmountmust be "1"
To use Payment applications you must have a Merchant Account. Please contact your Organization Profile Administrator to determine if you have a Merchant Account. If you do not, then the Organizational Profile Administrator must create a merchant account by selecting "Manage My Account" and then select "Setup Merchant Account".
After the merchant account is set up you will receive an email from amdocshub.com with the subject, "Notice from AT&T: Merchant Account Setup", that contains a "Merchant ID". This "Merchant ID" value must be placed in the Merchant ID field while creating an application.
The Payment API can provide a simple and safe process of enabling customers to purchase or subscribe to your app, which can potentially result in more sales for you, as developer. When you integrate the Payment API into your app, you get access to over 100 million AT&T subscribers, each of whom can place charges on his or her mobile invoice. This process does not involve long and hard-to-remember phone numbers to call and does not expose any credit card information.
- Subscriptions continue indefinitely until cancelled.
- Merchants may cancel subscriptions through the Refund API
- Customers may cancel subscriptions through the Online Assistance Center
- Customer Service Representatives may cancel subscriptions through the Customer Care Center
The following precautions must be observed in the handling your production client secret:
- The client secret shall only be distributed to authorized and trusted personnel.
- The client secret shall be stored on a secure server that is:
- Free from computer viruses and unauthorized software.
- Only accessible by authorized personnel and software.
- The client secret is only intended to be used in a server-to-server API request via HTTPS, (e.g. the Access Token resource and Notary service) and should not be transmitted or shared with client-facing applications.
- If unauthorized access of the client secret is detected, then the client secret must be changed immediately.
Go to the developer.att.com portal, sign up, accept the Terms and Conditions to gain access to our suite of Payment APIs, and finally, establish a merchant account.
There are no limits to the number of refunds by using the Refund Transaction method. However, if a customer claims five (5) refunds within a 90* day period through the AT&T Wireless customer care center, then that customer is placed on a Highly Refunded Activity (HRA) purchase blocker list which will suspend the purchase eligibility of the customer for 180 days.
*Configurable AT&T parameters (subject to updates).
AT&T requires that the consumer grant consent for all payment transactions. The consumer must acknowledge that they are buying a particular product, for a specific amount (taxes not included), sold by a particular application and merchant.
To make a purchase, users must authenticate themselves (via our OAuth 2.0-based process) by providing their AT&T Access ID / MSISDN and PIN.
Each purchase is signed by AT&T Notary API to ensure the payload cannot be tampered with.
The following notification types are supported:
- Refund Notification
- Recurrence Notification
- Stop Subscription Notification
- Cancel Subscription Notification
- Subscription Renewal Notification
Yes. Please note the following differences:
- For a Full Access account in the Sandbox environment; the purchases range from $0.00 through $24.99. For a Full Access account in the Production environment; the purchases range from $0.99 through $24.99.
- For a Full Access account in the Sandbox environment; 100% of the revenue is retained by AT&T. For a Full Access account in the Production environment; the revenue share is split 30/70 with AT&T retaining 30%.
- The service-level agreement (SLA), and the allowed transactions per second (TPS) differ between the two environments. For more information about these differences, please contact the Developer support team at email@example.com.
We provide a suite of reporting capabilities, including transaction-level details, summary reports, and settlement reports to help you manage your business.
Detailed reports can be requested by Submit a Ticket.
- For Single Pay transactions, keep the transaction ID generated at the end of the purchase process.
- For Subscriptions, keep the transaction ID, the merchant subscription ID, and the consumer ID.